updates

Author: craigshoemaker

articles/static-web-apps/local-development.md

@@ -61,7 +61,7 @@ swa start http://localhost:<DEV-SERVER-PORT-NUMBER> --api-location http://localh
 
 Optionally, if you use the `swa init` command, the Static Web Apps CLI looks at your application code and build a _swa-cli.config.json_ configuration file for the CLI. When you use the _swa-cli.config.json_ file, you can run `swa start` to launch your application locally.
 
-<sup>1</sup> The Azure Functions Core Tools are automatically installed by the CLI if they are not already on your system.
+<sup>1</sup> The Azure Functions Core Tools are automatically installed by the CLI if they aren't already on your system.
 
 ## Prerequisites
 
@@ -106,7 +106,7 @@ Open a terminal to the root folder of your existing Azure Static Web Apps site.
 | Serve a specific folder | `swa start ./<OUTPUT_FOLDER_NAME>` | Replace `<OUTPUT_FOLDER_NAME>` with the name of your output folder. |
 | Use a running framework development server | `swa start http://localhost:3000` | This command works when you have an instance of your application running under port `3000`. Update the port number if your configuration is different. |
 | Start a Functions app in a folder | `swa start ./<OUTPUT_FOLDER_NAME> --api-location ./api` | Replace `<OUTPUT_FOLDER_NAME>` with the name of your output folder. This command expects your application's API to have files in the _api_ folder. Update this value if your configuration is different. |
-| Use a running Functions app | `swa start ./<OUTPUT_FOLDER_NAME> --api-location http://localhost:7071` | Replace `<OUTPUT_FOLDER_NAME>` with the name of your output folder. This command expects your Azure Functions application the be available through port `7071`. Update the port number if your configuration is different. |
+| Use a running Functions app | `swa start ./<OUTPUT_FOLDER_NAME> --api-location http://localhost:7071` | Replace `<OUTPUT_FOLDER_NAME>` with the name of your output folder. This command expects your Azure Functions application to be available through port `7071`. Update the port number if your configuration is different. |
 
 ## Authorization and authentication emulation
 
@@ -126,6 +126,7 @@ The emulator provides a page allowing you to provide the following [client princ
 | **Username** | The account name associated with the security provider. This value appears as the `userDetails` property in the client principal and is autogenerated if you don't provide a value. |
 | **User ID** | Value autogenerated by the CLI.  |
 | **Roles** | A list of role names, where each name is on a new line.  |
+| **Claims** | A list of [user claims](user-information#client-principal-data), where each name is on a new line.  |
 
 Once logged in: