Acrolinx fixes on GitHub Actions

Author: jpconnock

articles/azure-app-configuration/concept-github-action.md

@@ -10,13 +10,13 @@ ms.service: azure-app-configuration
 
 ---
 # Sync your App Configuration instance using GitHub Actions
-Azure App Configuration uses GitHub Actions to update an App Configuration instance when triggered by an action performed on a GitHub repository. GitHub workflows can trigger app configuration updates, enabling the integration of those updates into the same workflow used to update the app code.
+Azure App Configuration uses GitHub Actions to trigger updates to an App Configuration instance based on actions performed on a GitHub repository. GitHub workflows trigger configuration updates, enabling the integration of those updates into the same workflow used to update the app code.
 
 A GitHub Actions [workflow](https://help.github.com/articles/about-github-actions#workflow) defines an automated process in a GitHub repository. This process tells GitHub how to build and deploy your GitHub project. Azure App Configuration provides the *Azure App Configuration Sync* Action to enable updates to an App Configuration instance when changes are made to the source repository. 
 
 A YAML (.yml) file found in the `/.github/workflows/` path of your repository defines your workflow. This definition contains the workflow's steps and parameters.
 
-GitHub events, such as a push to a repository, can trigger a GitHub Action workflow.  The *Azure App Configuration Sync* action enables you to trigger an update of an App Configuration instance when a specified GitHub action occurs. This allows you to leverage GitHub's core features when pushing, reviewing, or branching app configuration files just as you do with app code.
+GitHub events, such as a push to a repository, can trigger a GitHub Action workflow.  The *Azure App Configuration Sync* action enables you to trigger an update of an App Configuration instance when a specified GitHub action occurs. You can trigger configuration updates when pushing, reviewing, or branching app configuration files just as you do with app code.
 
 The GitHub [documentation](https://help.github.com/actions/automating-your-workflow-with-github-actions/configuring-a-workflow) provides in-depth view of GitHub workflows and actions. 
 
@@ -26,12 +26,12 @@ To start using this GitHub action, go to your repository and select the **Action
 > ![Select the Action tab](media/find-github-action.png)
 
 > [!div class="mx-imgBorder"]
-> ![Select the app configuration syn Action](media/app-configuration-sync-action.png)
+> ![Select the app configuration sync Action](media/app-configuration-sync-action.png)
 
 ## Sync configuration files after a push
 This action syncs Azure App Configuration files when a change is pushed to `appsettings.json`. When a developer pushes a change to `appsettings.json`, the App Configuration Sync action updates the App Configuration instance with the new values.
 
-The first section of this workflow specifies that the action triggers *on* a *push* containing `appsettings.json` to the *master* branch. The second section lists the jobs run once the action is triggered. The action checks out the relevant files and updates the App Configuration instance using the connection string stored as a secret in the repository.  For more information about using secrets in Github, see [GitHub's article](https://help.github.com/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets) about creating and using encrypted secrets.
+The first section of this workflow specifies that the action triggers *on* a *push* containing `appsettings.json` to the *master* branch. The second section lists the jobs run once the action is triggered. The action checks out the relevant files and updates the App Configuration instance using the connection string stored as a secret in the repository.  For more information about using secrets in GitHub, see [GitHub's article](https://help.github.com/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets) about creating and using encrypted secrets.
 
 ```json
 on: 
@@ -58,9 +58,9 @@ jobs:
 ```
 
 ## Use a dynamic label on sync
-The previous action updates the App Configuration instance whenever `appsettings.json` is updated. This action inserts a dynamic label on each sync, ensuring that each sync can be uniquely identified.  This allows code changes to quickly be mapped to config changes.
+The previous action updates the App Configuration instance whenever `appsettings.json` is updated. This action inserts a dynamic label on each sync, ensuring that each sync can be uniquely identified and allowing code changes to be mapped to config changes.
 
-The first section of this workflow specifies that the action triggers *on* a *push* containing `appsettings.json` to the *master* branch. The second section runs a job which creates a unique label for the config update based on the commit hash. The job then updates the App Configuration instance with the new values and the unique label for this update.
+The first section of this workflow specifies that the action triggers *on* a *push* containing `appsettings.json` to the *master* branch. The second section runs a job that creates a unique label for the config update based on the commit hash. The job then updates the App Configuration instance with the new values and the unique label for this update.
 
 ```json
 on: 
@@ -92,9 +92,9 @@ jobs:
 ```
 
 ## Use strict sync
-When strict mode is enabled, the sync ensures that the App Configuration instance matches the configuration file for the given prefix and label exactly. Key-value pairs with the same prefix and label that are not in the configuration file are deleted. 
+When strict mode is enabled, the sync ensures that the App Configuration instance matches the configuration file for the given prefix and label exactly. Key-value pairs with the same prefix and label that aren't in the configuration file are deleted. 
 
-If strict mode is not enabled, the sync will only set key-values from the configuration file. No key-value pairs will be deleted. 
+If strict mode isn't enabled, the sync will only set key-values from the configuration file. No key-value pairs will be deleted. 
 
 ```json
 on: 
@@ -167,7 +167,7 @@ jobs:
           depth: 2 
 ```
 
-Given a depth of 2, the example above now returns the following key:value pair:
+Given a depth of 2, the example above now returns the following key-value pair:
 
 | Key | Value |
 | --- | --- |
@@ -182,7 +182,7 @@ Input parameters specify data used by the action during runtime.  The following
 
 | Input name | Required? | Value |
 |----|----|----|
-| configurationFile | Yes | Path to the configuration file in the repository, relative to the root of the repository.  Glob patterns are supported and can include multiple files. |
+| configurationFile | Yes | Relative path to the configuration file in the repository.  Glob patterns are supported and can include multiple files. |
 | format | Yes | File format of the configuration file.  Valid formats are: JSON, YAML, properties. |
 | connectionString | Yes | Connection string for the App Configuration instance. The connection string should be stored as a secret in the GitHub repository, and only the secret name should be used in the workflow. |
 | separator | Yes | Separator used when flattening the configuration file to key-value pairs.  Valid values are: . , ; : - _ __ / |