replaced link for ghi #97749

Author: chcomley

articles/static-web-apps/branch-environments.md

@@ -5,7 +5,7 @@ author: craigshoemaker
 ms.author: cshoe
 ms.service: static-web-apps
 ms.topic: conceptual
-ms.date: 03/29/2022
+ms.date: 09/19/2022
 ms.custom: template-how-to
 ---
 
@@ -15,9 +15,9 @@ You can configure your site to deploy every change made to branches that aren't
 
 ## Configuration
 
-To enable stable URL environments, make the following changes to your [configuration file](configuration.md).
+To enable stable URL environments, make the following changes to your [configuration .yml file](build-configuration.md?tabs=github-actions).
 
-- Set the `production_branch` input to your production branch name on the `static-web-apps-deploy` job in GitHub action or on the AzureStaticWebApp task. This ensures changes to your production branch are deployed to the production environment, while changes to other branches are deployed to a preview environment.
+- Set the `production_branch` input to your production branch name on the `static-web-apps-deploy` job in GitHub action or on the AzureStaticWebApp task. This action ensures changes to your production branch are deployed to the production environment, while changes to other branches are deployed to a preview environment.
 - List the branches you want to deploy to preview environments in the trigger array in your workflow configuration so that changes to those branches also trigger the GitHub Actions or Azure Pipelines deployment.
   - Set this array to `**` for GitHub Actions or `*` for Azure Pipelines if you want to track all branches.
 
@@ -83,7 +83,7 @@ steps:
 
 In this example, the preview environments are defined for the `dev` and `staging` branches. Each branch is deployed to a separate preview environment.
 
-## Next Steps
+## Next steps
 
 > [!div class="nextstepaction"]
 > [Create named preview environments](./named-environments.md)