minor updates in provider doc file

Signed-off-by: Aditya Kumar <aditya.kumar60@infosys.com>

docs/auth/auth0/provider.md

@@ -22,10 +22,10 @@ provider that can authenticate users using OAuth.
 3. Create an Application
    - Name: Backstage (or your custom app name)
    - Application type: Single Page Web Application
-4. Click on the Settings tab
+4. Click on the Settings tab.
 5. Add under `Application URIs` > `Allowed Callback URLs`:
    `http://localhost:7007/api/auth/auth0/handler/frame`
-6. Click `Save Changes`
+6. Click `Save Changes`.
 
 ## Configuration
 
@@ -50,10 +50,10 @@ auth:
 
 The Auth0 provider is a structure with these configuration keys:
 
-- `clientId`: The Application client ID, found on the Auth0 Application page
+- `clientId`: The Application client ID, found on the Auth0 Application page.
 - `clientSecret`: The Application client secret, found on the Auth0 Application
-  page
-- `domain`: The Application domain, found on the Auth0 Application page
+  page.
+- `domain`: The Application domain, found on the Auth0 Application page.
 
 It additionally relies on the following configuration to function:
 
@@ -63,16 +63,16 @@ Auth0 requires a session, so you need to give the session a secret key.
 
 ### Optional
 
-- `audience`: The intended recipients of the token
+- `audience`: The intended recipients of the token.
 - `connection`: Social identity provider name. To check the available social connections, please visit [Auth0 Social Connections](https://marketplace.auth0.com/features/social-connections).
-- `connectionScope`: Additional scopes in the interactive token request. It should always be used in combination with the `connection` parameter
+- `connectionScope`: Additional scopes in the interactive token request. It should always be used in combination with the `connection` parameter.
 
 ### Resolvers
 
 This provider includes several resolvers out of the box that you can use:
 
-- `emailMatchingUserEntityProfileEmail`: Matches the email address from the auth provider with the User entity that has a matching `spec.profile.email`. If no match is found it will throw a `NotFoundError`.
-- `emailLocalPartMatchingUserEntityName`: Matches the [local part](https://en.wikipedia.org/wiki/Email_address#Local-part) of the email address from the auth provider with the User entity that has a matching `name`. If no match is found it will throw a `NotFoundError`.
+- `emailMatchingUserEntityProfileEmail`: Matches the email address from the auth provider with the User entity that has a matching `spec.profile.email`. If no match is found, it will throw a `NotFoundError`.
+- `emailLocalPartMatchingUserEntityName`: Matches the [local part](https://en.wikipedia.org/wiki/Email_address#Local-part) of the email address from the auth provider with the User entity that has a matching `name`. If no match is found, it will throw a `NotFoundError`.
 
 :::note Note
 
@@ -80,11 +80,11 @@ The resolvers will be tried in order, but will only be skipped if they throw a `
 
 :::
 
-If these resolvers do not fit your needs you can build a custom resolver, this is covered in the [Building Custom Resolvers](../identity-resolver.md#building-custom-resolvers) section of the Sign-in Identities and Resolvers documentation.
+If these resolvers do not fit your needs, you can build a custom resolver, this is covered in the [Building Custom Resolvers](../identity-resolver.md#building-custom-resolvers) section of the Sign-in Identities and Resolvers documentation.
 
 ## Backend Installation
 
-To add the provider to the backend we will first need to install the package by running this command:
+To add the provider to the backend, we will first need to install the package by running this command:
 
 ```bash title="from your Backstage root directory"
 yarn --cwd packages/backend add @backstage/plugin-auth-backend-module-auth0-provider