quick fixes

docs/ca/dev/add-variables-in-the-parameter-store.md

@@ -29,7 +29,7 @@ For complex or system-critical changes to variables, we recommend consulting wit
 
 There are two types of environment variables: customer-owned and Spryker-owned.
 
-Spryker-owned variables are managed and can be updated only with the help of Spryker Cloud or support teams.
+Spryker-owned variables are managed and can be updated only with the help of Spryker Cloud or support teams. To request a variable change, in [Support Portal](https://support.spryker.com/), create the following request: Infrastructure Change Request > Change to existing parameter store variable.
 
 Customer-owned variables are created and managed by you or implementation partner. You have full control over these variables and can add or edit them according to your needs. Changes to these variables don't automatically propagate into a running environment. To apply changes made to your environment variables, you need to run an ECS-updater-* pipeline to bring them to the containers or run a full redeploy. You can do this whole process without creating support tickets.
 

docs/ca/dev/connect-a-code-repository.md

@@ -48,9 +48,10 @@ We recommend mapping your branches to environments as follows:
   This opens the pipeline editing page.  
 5. In the **Edit: Source** pane, click **Edit stage**.  
 6. In the **Spryker_App_Src** section, click the *Edit action* button.
+  This opens the **Edit action** window.
+
 ![edit-action](https://spryker.s3.eu-central-1.amazonaws.com/docs/ca/dev/connect-a-code-repository.md/edit-action.png)
 
-This opens the **Edit action** window.
 7. For **Action provider**, select **GitHub(via GitHub App)**.
 This adds GitHub related fields to the window.
 8. Click **Connect to GitHub** and authorize AWS CodePipeline to access your GitHub repository.