Merge pull request #114557 from craigshoemaker/marm-clean-up

Update drafts

Author: PRMerger13

articles/static-web-apps/authentication-authorization.md

@@ -21,6 +21,8 @@ Azure Static Web Apps streamlines the authentication experience by managing auth
 
 Provider-specific [invitations](#invitations) associate users with roles, and authorized users are granted access to [routes](routes.md) by rules defined in the _routes.json_ file.
 
+All authentication providers are enabled by default. To restrict an authentication provider, [block access](#block-an-authorization-provider) with a custom route rule.
+
 The topics of authentication and authorization significantly overlap with routing concepts. Make sure to read the [routing guide](routes.md) along with this article.
 
 ## Roles
@@ -96,6 +98,8 @@ As you remove a user, keep in mind the following items:
 1. Worldwide propagation may take a few minutes.
 1. If the user is added back to the app, the [`userId` changes](user-information.md).
 
+## Remove personal identifying information
+
 When you grant consent to an application as an end-user, the application has access to your email address or your username depending on the identity provider. Once this information is provided, the owner of the application decides how to manage personally identifying information.
 
 End-users need to contact administrators of individual web apps to to revoke this information from their systems.

articles/static-web-apps/github-actions-workflow.md

@@ -137,13 +137,9 @@ with:
 
 The `repo_token`, `action`, and `azure_static_web_apps_api_token` values are set for you by Azure Static Web Apps shouldn't be manually changed.
 
-## Customizations
+## Custom build commands
 
-There are few additional configuration settings available that are not generated in the workflow file by default. The following customizations can be defined under a job's `with` section.
-
-### Custom build commands
-
-You can have fine-grained control over what commands run during a deployment.
+You can have fine-grained control over what commands run during a deployment. The following commands can be defined under a job's `with` section.
 
 The deployment always calls `npm install` before any custom command.
 
@@ -152,11 +148,15 @@ The deployment always calls `npm install` before any custom command.
 | `app_build_command` | Defines a custom command to run during deployment of the static content application.<br><br>For example, to configure a production build for an Angular application enter `ng build -prod`. If left blank, the workflow tries to run the `build` or `build:Azure` commands.  |
 | `api_build_command` | Defines a custom command to run during deployment of the Azure Functions API application. |
 
-### Route file location
+## Route file location
 
-You can customize the workflow to look for the [routes.json](routes.md) in any folder in your repository. The `routes_location` property defines the directory location where the _routes.json_ file is found. This location is relative to the root of the repository.
+You can customize the workflow to look for the [routes.json](routes.md) in any folder in your repository. The following property can be defined under a job's `with` section.
+
+| Property            | Description |
+|---------------------|-------------|
+| `routes_location` | Defines the directory location where the _routes.json_ file is found. This location is relative to the root of the repository. |
 
-Being explicit about the location of your _routes.json_ file is particularly important if your front-end framework build step does not move this file to the `app_artifact_location` by default.
+ Being explicit about the location of your _routes.json_ file is particularly important if your front-end framework build step does not move this file to the `app_artifact_location` by default.
 
 ## Next steps