Reported errors, typos, and broken/incorrect links (#566)

* Typos and broken links

* Adressed comments

Author: avanscoy

main/docs/authenticate/database-connections/custom-db/templates/get-user.mdx

@@ -4,7 +4,7 @@ title: Get User Script Templates
 ---
 The Get User script implements the function executed to determine the current state of existence of a user. We recommend naming this function `getUser`.
 
-This script is required for [automatic migration](/docs/manage-users/user-migration/configure-automatic-migration-from-your-database), and conditionally required for legacy authentication depending on the operations configured for the connection. To avoid creating duplicate users, set a consistent, unchanging `user_id` on the returned user profile for the same user.
+This script is required for [automatic migration](/docs/manage-users/user-migration/configure-automatic-migration-from-your-database), and conditionally required for legacy authentication depending on the operations configured for the connection. Auth0 recommends you set permanent `user_id` on the returned user profile to avoid creating duplicate users.
 
 If automatic migration is configured for the connection and the user profile has not yet been created, the script is executed whenever the following operations occur:
 

main/docs/authenticate/database-connections/custom-db/templates/login.mdx

@@ -4,7 +4,7 @@ title: Login Script Templates
 ---
 The Login script implements the function executed each time a user is required to authenticate. We recommend naming this function `login`.
 
-This script is required for both legacy authentication and for [automatic migration](/docs/manage-users/user-migration/configure-automatic-migration-from-your-database). If automatic migration is configured for the connection, the migration process will be triggered after the first time the user logs in successfully.
+This script is required for both legacy authentication and for [automatic migration](/docs/manage-users/user-migration/configure-automatic-migration-from-your-database). If automatic migration is configured for the connection, the migration process triggers after the first time the user logs in successfully. Auth0 recommends you set permanent `user_id` on the returned user profile to avoid creating duplicate users.
 
 ## Login function
 

main/docs/authenticate/login/max-age-reauthentication.mdx

@@ -1,12 +1,12 @@
 ---
-description: Describes how to use the max_age authentication request parameter as a mechanism whereby relying parties can positively confirm that re-authentication has taken place within a given time interval.
+description: Describes how relying parties are able to confirm re-authentication has taken place at a specific time interval by using the `max_age` request parameter. 
 title: Force Reauthentication in OIDC
 ---
-The `prompt=login` mechanism can be subverted by simply stripping the parameter as it passes through the user agent (browser) and is only good for providing a UX hint to the <Tooltip tip="OpenID: Open standard for authentication that allows applications to verify users' identities without collecting and storing login information." cta="View Glossary" href="/docs/glossary?term=OpenID">OpenID</Tooltip> provider (OP) in cases when the <Tooltip tip="OpenID: Open standard for authentication that allows applications to verify users' identities without collecting and storing login information." cta="View Glossary" href="/docs/glossary?term=relying+party">relying party</Tooltip> (RP) wants to display a link like:
+The `prompt=login` mechanism can be subverted by simply stripping the parameter as it passes through the user agent (browser) and is only good for providing a UX hint to the <Tooltip tip="OpenID: Open standard for authentication that allows applications to verify users' identities without collecting and storing login information." cta="View Glossary" href="/docs/glossary?term=OpenID">OpenID</Tooltip> provider (OP) in cases when the <Tooltip tip="Relying Party: Entity (such as a service or application) that depends on a third-party identity provider to authenticate a user." cta="View Glossary" href="/docs/glossary?term=relying+party">relying party</Tooltip> (RP) wants to display a link like:
 
 **“Hi Josh. Not you? Click here.”**
 
-However, you should not rely on it to validate that a fresh authentication took place. To mitigate this, the client must validate that re-authentication has taken place using the `auth_time` claim if re-authentication is why`max_age`was requested. This claim will be included automatically in the <Tooltip tip="ID Token: Credential meant for the client itself, rather than for accessing a resource." cta="View Glossary" href="/docs/glossary?term=ID+token">ID token</Tooltip> when `prompt-login` or `max_age=0` parameters are given in the authentication request.
+However, you should not rely on it to validate that a fresh authentication took place. To mitigate this, the client must validate that re-authentication has taken place using the `auth_time` claim. This claim will be included automatically in the <Tooltip tip="ID Token: Credential meant for the client itself, rather than for accessing a resource." cta="View Glossary" href="/docs/glossary?term=ID+token">ID token</Tooltip> when `prompt=login` or `max_age=0` parameters are given in the authentication request.
 
 You need to pass the `max_age` parameter to the Authorization API [`/authorize` endpoint](https://auth0.com/docs/api/authentication). If you use [Auth0.js](/docs/libraries/auth0js) or [Lock](/docs/libraries/lock/lock-authentication-parameters), you can set the parameter in the appropriate options of the library.
 

main/docs/customize/phone-messages/configure-phone-messaging-providers/configure-a-custom-phone-provider/configure-a-custom-phone-provider-with-terraform.mdx

@@ -61,6 +61,7 @@ resource "auth0_trigger_action" "custom_phone_provider" {
   depends_on = [
     auth0_action.custom_phone_provider
   ]
+}
 ```
 
 
@@ -79,6 +80,7 @@ resource "auth0_phone_provider" "custom_phone_provider" {
     delivery_methods = ["text", "voice"]
   }
   credentials {}
+},
 ```
 
 
@@ -97,4 +99,4 @@ You may have multiple custom provider Actions with `deploy: true`. Auth0 has a m
 * If you encounter this scenario, it’s recommended that you [list your Actions](https://auth0.com/docs/api/management/v2/actions/get-actions) to identify any duplicates to delete.
 * If you encounter this scenario after managing your custom providers through multiple methods (Terraform, Auth0 Dashboard, <Tooltip tip="Management API: A product to allow customers to perform administrative tasks." cta="View Glossary" href="/docs/glossary?term=Management+API">Management API</Tooltip>, and/or Auth0 SDKs) it is advisable to reset the custom provider configuration. We recommend you refrain from using multiple methods to manage your custom provider.
 
-To reset the custom phone provider, navigate to [Auth0 Dashboard > Branding](https://manage.auth0.com/#/branding) and select **Phone Provider**. Then, select the **Reset** button to restore your custom provider to its default.
+To reset the custom phone provider, navigate to [Auth0 Dashboard > Branding > Phone Provider](https://manage.auth0.com/#/phone/templates/phone/provider). Then, select the **Reset** button under Provider Configuration to restore your custom provider to its default.