Small changes to add-api

Author: Adrian Hall

articles/static-web-apps/add-api.md

@@ -34,6 +34,12 @@ You can add serverless APIs to Azure Static Web Apps that are powered by Azure F
 
 Before adding an API, create and deploy a frontend application to Azure Static Web Apps. Use an existing app that you've already deployed or create one by following the [Building your first static site with Azure Static Web Apps](getting-started.md) quickstart.
 
+Once you have a frontend application deployed to Azure Static Web Apps, [clone your app repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository). For example, to clone using the `git` command line:
+
+```bash
+git clone https://github.com/_username_/my-first-static-web-app
+```
+
 In Visual Studio Code, open the root of your app's repository. The folder structure contains the source for your frontend app and the Static Web Apps GitHub workflow in _.github/workflows_ folder.
 
 ```Files
@@ -233,6 +239,7 @@ Ensure you have the necessary command line tools installed.
 npm install -g @azure/static-web-apps-cli
 ```
 
+> [!TIP]
 > If you don't want to install the `swa` command line globally, you can use `npx swa` instead of `swa` in the following instructions.
 
 ### Build frontend app
@@ -272,7 +279,7 @@ npm run build
 
 ---
 
-### Start the CLI
+### Run the application locally
 
 Run the frontend app and API together by starting the app with the Static Web Apps CLI. Running the two parts of your application this way allows the CLI to serve your frontend's build output from a folder, and makes the API accessible to the running app.
 
@@ -312,9 +319,11 @@ Run the frontend app and API together by starting the app with the Static Web Ap
 
     ---
 
-1. When the CLI processes start, access your app at `http://localhost:4280/`. Notice how the page calls the API and displays its output, `Hello from the API`.
+1. Windows Firewall may prompt to request that the Azure Functions runtime can access the Internet.  If this happens, select **Allow**.
+   
+2. When the CLI processes start, access your app at `http://localhost:4280/`. Notice how the page calls the API and displays its output, `Hello from the API`.
 
-1. To stop the CLI, type <kbd>Ctrl + C</kbd>.
+3. To stop the CLI, type <kbd>Ctrl + C</kbd>.
 
 ## Add API location to workflow
 
@@ -323,6 +332,16 @@ Before you can deploy your app to Azure, update your repository's GitHub Actions
 1. Open your workflow at _.github/workflows/azure-static-web-apps-\<DEFAULT-HOSTNAME>.yml_.
 
 1. Search for the property `api_location` and set the value to `api`.
+
+   ```yaml
+   ###### Repository/Build Configurations - These values can be configured to match your app requirements. ######
+   # For more information regarding Static Web App workflow configurations, please visit: https://aka.ms/swaworkflowconfig
+   app_location: "/" # App source code path
+   api_location: "api" # Api source code path - optional
+   output_location: "build" # Built app content directory - optional
+   ###### End of Repository/Build Configurations ######
+   ```
+
 1. Save the file.
 
 ## Deploy changes