diff --git a/articles/_includes/_web_origins.md b/articles/_includes/_web_origins.md
index 57364906f5..27ba7150f1 100644
--- a/articles/_includes/_web_origins.md
+++ b/articles/_includes/_web_origins.md
@@ -2,4 +2,4 @@
### Configure Allowed Web Origins
-You need to add the URL for your app to the **Allowed Web Origins** field in your [Application Settings](${manage_url}/#/applications/${account.clientId}/settings). If you don't register your application URL here, the application will be unable to silently refresh the authentication tokens and your users will be logged out the next time they visit the application, or refresh the page.
+You need to add the URL for your app to the **Allowed Web Origins** field in your Application Settings. If you don't register your application URL here, the application will be unable to silently refresh the authentication tokens and your users will be logged out the next time they visit the application, or refresh the page.
\ No newline at end of file
diff --git a/articles/api-auth/tutorials/adoption/authorization-code.md b/articles/api-auth/tutorials/adoption/authorization-code.md
index 073cef649a..692a46e71f 100644
--- a/articles/api-auth/tutorials/adoption/authorization-code.md
+++ b/articles/api-auth/tutorials/adoption/authorization-code.md
@@ -147,7 +147,7 @@ Pragma: no-cache
"id_token": "eyJ..."
}
- - The returned Access Token is valid for optionally calling the API specified in the
audience
parameter and the /userinfo endpoint (provided that the API uses RS256
as the signing algorithm and openid
is used as a scope
parameter). If you are not implementing your own Resource Server (API), then you can use https://{$account.namespace}/userinfo
as the audience
parameter, which will return an opaque Access Token.
+ - The returned Access Token is valid for optionally calling the API specified in the
audience
parameter and the /userinfo endpoint (provided that the API uses RS256
as the signing algorithm and openid
is used as a scope
parameter). If you are not implementing your own Resource Server (API), then you can use https://${account.namespace}/userinfo
as the audience
parameter, which will return an opaque Access Token.
- A Refresh Token will be returned only if the
offline_access
scope was granted.
@@ -224,7 +224,7 @@ Pragma: no-cache
"scope": "openid email"
}
- - The returned Access Token is valid for optionally calling the API specified in the
audience
parameter and the /userinfo endpoint (provided that the API uses RS256
as the signing algorithm and openid
is used as a scope
parameter). If you are not implementing your own Resource Server (API), then you can use https://{$account.namespace}/userinfo
as the audience
parameter, which will return an opaque Access Token.
+ - The returned Access Token is valid for optionally calling the API specified in the
audience
parameter and the /userinfo endpoint (provided that the API uses RS256
as the signing algorithm and openid
is used as a scope
parameter). If you are not implementing your own Resource Server (API), then you can use https://${account.namespace}/userinfo
as the audience
parameter, which will return an opaque Access Token.
diff --git a/articles/flows/guides/device-auth/includes/index.md b/articles/flows/guides/device-auth/includes/index.md
index a53a98ad47..a7fdf8b8f3 100644
--- a/articles/flows/guides/device-auth/includes/index.md
+++ b/articles/flows/guides/device-auth/includes/index.md
@@ -1,10 +1,10 @@
::: note
-This tutorial will help you call your own API from an input-constrained device using the Device Authorization Flow. If you want to learn how the flow works and why you should use it, see [Device Authorization Flow](/flows/concepts/device-auth).
+This tutorial will help you call your own API from an input-constrained device using the Device Authorization Flow. If you want to learn how the flow works and why you should use it, see Device Authorization Flow.
:::
Auth0 makes it easy for your app to implement the Device Authorization flow using:
-* Authentication API: Keep reading to learn how to call our API directly. For an interactive experience, see our [Device Flow Playground](https://auth0.github.io/device-flow-playground/).
+* Authentication API: Keep reading to learn how to call our API directly. For an interactive experience, see our Device Flow Playground.
## Prerequisites
@@ -12,19 +12,19 @@ Auth0 makes it easy for your app to implement the Device Authorization flow usin
* Check [limitations](#limitations) to be sure the Device Authorization flow is suitable for your implementation.
-* [Register the Application with Auth0](/dashboard/guides/applications/register-app-native).
+* Register the Application with Auth0.
* Select an **Application Type** of **Native**.
* If necessary, set **Allowed Web Origins**. You can use this to allow localhost as an origin for local development, or to set an allowed origin for specific TV software with architecture subject to CORS (eg: HTML5 + JS). Most applications will not use this setting.
- * Ensure that the **OIDC Conformant** toggle is enabled. This setting is in the [Dashboard](${manage_url}) under **Application Settings > Advanced > OAuth**.
- * Make sure the Application's **[Grant Types](/dashboard/guides/applications/update-grant-types)** include **Device Code**. This is also in the [Dashboard](${manage_url}), under **Application Settings > Advanced > Grant Types**.
- * If you want your Application to be able to use [Refresh Tokens](/tokens/concepts/refresh-tokens), make sure the Application's **[Grant Types](/dashboard/guides/applications/update-grant-types)** include **Refresh Token**.
+ * Ensure that the **OIDC Conformant** toggle is enabled. This setting is in the Dashboard under **Application Settings > Advanced > OAuth**.
+ * Make sure the Application's **Grant Types** include **Device Code**. This is also in the Dashboard, under **Application Settings > Advanced > Grant Types**.
+ * If you want your Application to be able to use Refresh Tokens, make sure the Application's **Grant Types** include **Refresh Token**.
-* Set up and enable at least one connection for the Application: [Database connections](/dashboard/guides/connections/set-up-connections-database), [Social connections](/dashboard/guides/connections/set-up-connections-social)
+* Set up and enable at least one connection for the Application: Database connections, Social connections
-* [Register your API with Auth0](/architecture-scenarios/mobile-api/part-2#create-the-api)
- * If you want your API to receive [Refresh Tokens](/tokens/concepts/refresh-tokens) to allow it to obtain new tokens when the previous ones expire, enable **Allow Offline Access**.
+* Register your API with Auth0
+ * If you want your API to receive Refresh Tokens to allow it to obtain new tokens when the previous ones expire, enable **Allow Offline Access**.
-* [Configure Device User Code Settings](/dashboard/guides/tenants/configure-device-user-code-settings) to define the character set, format, and length of your randomly-generated user code.
+* Configure Device User Code Settings to define the character set, format, and length of your randomly-generated user code.
## Steps
@@ -60,7 +60,7 @@ Optional: [Troubleshooting](#troubleshooting)
## Keep reading
-- [The OAuth 2.0 protocol](/protocols/oauth2)
-- [The OpenID Connect protocol](/protocols/oidc)
-- [Tokens](/tokens)
-- [Tenant Logs for Devices](/logs)
+- The OAuth 2.0 protocol
+- The OpenID Connect protocol
+- Tokens
+- Tenant Logs for Devices
diff --git a/articles/quickstart/_includes/_auth0-react-install.md b/articles/quickstart/_includes/_auth0-react-install.md
index 8dedf06669..3a0ce623ed 100644
--- a/articles/quickstart/_includes/_auth0-react-install.md
+++ b/articles/quickstart/_includes/_auth0-react-install.md
@@ -8,4 +8,4 @@ Run the following command within your project directory to install the Auth0 Rea
npm install @auth0/auth0-react
```
-The SDK exposes methods and variables that help you integrate Auth0 with your React application idiomatically using React Hooks or Higher-Order Components.
\ No newline at end of file
+The SDK exposes methods and variables that help you integrate Auth0 with your React application idiomatically using React Hooks or Higher-Order Components.
\ No newline at end of file
diff --git a/articles/quickstart/backend/_includes/_api_create_new.md b/articles/quickstart/backend/_includes/_api_create_new.md
index 9159c08aa7..5e1ef09c11 100644
--- a/articles/quickstart/backend/_includes/_api_create_new.md
+++ b/articles/quickstart/backend/_includes/_api_create_new.md
@@ -2,7 +2,7 @@
### Create an API
-In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API, for example, `https://quickstarts/api`. You will use the identifier as an `audience` later, when you are configuring the Access Token verification. Leave the **Signing Algorithm** as **RS256**.
+In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API, for example, `https://quickstarts/api`. You will use the identifier as an `audience` later, when you are configuring the Access Token verification. Leave the **Signing Algorithm** as **RS256**.

diff --git a/articles/quickstart/backend/_includes/_api_create_new_2.md b/articles/quickstart/backend/_includes/_api_create_new_2.md
index 9560392fc3..ea482527b1 100644
--- a/articles/quickstart/backend/_includes/_api_create_new_2.md
+++ b/articles/quickstart/backend/_includes/_api_create_new_2.md
@@ -1,5 +1,5 @@
## Create a Resource Server (API)
-In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API, for example, `https://quickstarts/api`. You will use the identifier as an `audience` later, when you are configuring the Access Token verification. For **Signing Algorithm**, select **RS256**.
+In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API, for example, `https://quickstarts/api`. You will use the identifier as an `audience` later, when you are configuring the Access Token verification. For **Signing Algorithm**, select **RS256**.

\ No newline at end of file
diff --git a/articles/quickstart/backend/_includes/_api_jwks_description.md b/articles/quickstart/backend/_includes/_api_jwks_description.md
index 09dfc32ecc..21e2fd0987 100644
--- a/articles/quickstart/backend/_includes/_api_jwks_description.md
+++ b/articles/quickstart/backend/_includes/_api_jwks_description.md
@@ -1,7 +1,7 @@
-By default, your API uses RS256 as the algorithm for signing tokens. Since RS256 uses a private/public keypair, it verifies the tokens against the public key for your Auth0 account. The public key is in the JSON Web Key Set (JWKS) format, and can be accessed here.
+By default, your API uses RS256 as the algorithm for signing tokens. Since RS256 uses a private/public keypair, it verifies the tokens against the public key for your Auth0 account. The public key is in the JSON Web Key Set (JWKS) format, and can be accessed here.
<% if (typeof sampleLink == 'string') { %>
::: note
-We recommend using the default RS256 signing algorithm for your API. If you need to use the HS256 algorithm, see the HS256 integration sample.
+We recommend using the default RS256 signing algorithm for your API. If you need to use the HS256 algorithm, see the HS256 integration sample.
:::
<% } %>
diff --git a/articles/quickstart/backend/_includes/_api_jwks_description_no_link.md b/articles/quickstart/backend/_includes/_api_jwks_description_no_link.md
index d37f41ce8d..f5a8fb5a20 100644
--- a/articles/quickstart/backend/_includes/_api_jwks_description_no_link.md
+++ b/articles/quickstart/backend/_includes/_api_jwks_description_no_link.md
@@ -1 +1 @@
-By default, your API will be set up to use RS256 as the algorithm for signing tokens. Since RS256 works by using a private/public keypair, tokens can be verified against the public key for your Auth0 account. This public key is accessible at https://${account.namespace}/.well-known/jwks.json.
\ No newline at end of file
+By default, your API will be set up to use RS256 as the algorithm for signing tokens. Since RS256 works by using a private/public keypair, tokens can be verified against the public key for your Auth0 account. This public key is accessible at https://${account.namespace}/.well-known/jwks.json.
\ No newline at end of file
diff --git a/articles/quickstart/backend/_includes/_api_scopes_access_resources.md b/articles/quickstart/backend/_includes/_api_scopes_access_resources.md
index 0932c204e5..83005290e6 100644
--- a/articles/quickstart/backend/_includes/_api_scopes_access_resources.md
+++ b/articles/quickstart/backend/_includes/_api_scopes_access_resources.md
@@ -1,6 +1,6 @@
Permissions let you define how resources can be accessed on behalf of the user with a given access token. For example, you might choose to grant read access to the `messages` resource if users have the manager access level, and a write access to that resource if they have the administrator access level.
-You can define allowed permissions in the **Permissions** view of the Auth0 Dashboard's APIs section.
+You can define allowed permissions in the **Permissions** view of the Auth0 Dashboard's APIs section.

diff --git a/articles/quickstart/backend/_includes/_api_using.md b/articles/quickstart/backend/_includes/_api_using.md
index 3ecbb25a8f..e8ef53ce4f 100644
--- a/articles/quickstart/backend/_includes/_api_using.md
+++ b/articles/quickstart/backend/_includes/_api_using.md
@@ -21,7 +21,7 @@ If you are calling the API from a Single-Page Application or a Mobile/Native app
* Single-Page Applications
* Mobile / Native Application
-If you are calling the API from a command-line tool or another service, where there isn't a user entering their credentials, you need to use the OAuth Client Credentials flow. To do that, register a Machine to Machine Application, and then subsequently use the **Client ID** and **Client Secret** of this application when making the request below and pass those along in the `client_id` and `client_secret` parameters respectively. Also include the Audience for the API you want to call.
+If you are calling the API from a command-line tool or another service, where there isn't a user entering their credentials, you need to use the OAuth Client Credentials flow. To do that, register a Machine to Machine Application, and then subsequently use the **Client ID** and **Client Secret** of this application when making the request below and pass those along in the `client_id` and `client_secret` parameters respectively. Also include the Audience for the API you want to call.
:::note
Read Application Settings for more information on getting the Client ID and Client Secret for your machine-to-machine app.
@@ -62,7 +62,7 @@ Read API settings.
+For testing purposes, you can also get an Access Token from the **Test** tab in your API settings.
## Test Your API
diff --git a/articles/quickstart/backend/_includes/_call_api.md b/articles/quickstart/backend/_includes/_call_api.md
index 19de58a6f6..93bea21fc7 100644
--- a/articles/quickstart/backend/_includes/_call_api.md
+++ b/articles/quickstart/backend/_includes/_call_api.md
@@ -2,7 +2,7 @@
### Make a Call to Your API
-To make calls to your API, you need an Access Token. You can get an Access Token for testing purposes from the **Test** view in your API settings.
+To make calls to your API, you need an Access Token. You can get an Access Token for testing purposes from the **Test** view in your API settings.

diff --git a/articles/quickstart/backend/aspnet-core-webapi/interactive.md b/articles/quickstart/backend/aspnet-core-webapi/interactive.md
index 33bcece34e..75b911693b 100644
--- a/articles/quickstart/backend/aspnet-core-webapi/interactive.md
+++ b/articles/quickstart/backend/aspnet-core-webapi/interactive.md
@@ -89,7 +89,7 @@ Regardless of the type of application you are developing or the framework you ar
If you are calling your API from a Single-Page Application (SPA) or a Native application, after the authorization flow completes, you will get an access token.
-If you are calling the API from a command-line tool or another service where a user entering credentials does not exist, use the OAuth Client Credentials Flow. To do so, register a Machine-to-Machine Application, and pass in the **Client ID** as the `client_id` parameter, the **Client Secret** as the `client_secret` parameter, and the API Identifier (the same value you used to configure the middleware earlier in this quickstart) as the `audience` parameter when making the following request:
+If you are calling the API from a command-line tool or another service where a user entering credentials does not exist, use the OAuth Client Credentials Flow. To do so, register a Machine-to-Machine Application, and pass in the **Client ID** as the `client_id` parameter, the **Client Secret** as the `client_secret` parameter, and the API Identifier (the same value you used to configure the middleware earlier in this quickstart) as the `audience` parameter when making the following request:
:::note
To learn more about getting the Client ID and Client Secret for your machine-to-machine application, read Application Settings.
diff --git a/articles/quickstart/backend/django/interactive.md b/articles/quickstart/backend/django/interactive.md
index 78cf320ae7..458d147557 100644
--- a/articles/quickstart/backend/django/interactive.md
+++ b/articles/quickstart/backend/django/interactive.md
@@ -53,7 +53,7 @@ cd apiexample
## Create the JWT validator {{{ data-action=code data-code="apiexample/validator.py" }}}
-You're going to use a library called Authlib to create a ResourceProtector, which is a type of Django view decorator that protects your resources (API views) with a given validator.
+You're going to use a library called Authlib to create a ResourceProtector, which is a type of Django view decorator that protects your resources (API views) with a given validator.
The validator will verify the Access Token that you pass to the resource by checking that it has a valid signature and claims.
diff --git a/articles/quickstart/backend/java-spring-security5/interactive.md b/articles/quickstart/backend/java-spring-security5/interactive.md
index 0cbff124c9..ae88837d54 100644
--- a/articles/quickstart/backend/java-spring-security5/interactive.md
+++ b/articles/quickstart/backend/java-spring-security5/interactive.md
@@ -107,7 +107,7 @@ To make your endpoint return a JSON, you can use a Java record. The member varia
## Create the API controller {{{ data-action=code data-code="APIController.java" }}}
-Create a new class named `APIController` to handle requests to the endpoints. The `APIController` has three routes as defined in the Protect API Endpoints section. For this example, allow all origins through `@CrossOrigin` annotation. Real applications should configure `CORS` for their use case.
+Create a new class named `APIController` to handle requests to the endpoints. The `APIController` has three routes as defined in the [Protect API Endpoints](/quickstart/backend/java-spring-security5/interactive/#configure-the-resource-server) section. For this example, allow all origins through `@CrossOrigin` annotation. Real applications should configure `CORS` for their use case.
## Run the application {{{ data-action=code data-code="APIController.java" }}}
diff --git a/articles/quickstart/backend/rails/01-authorization.md b/articles/quickstart/backend/rails/01-authorization.md
index 327cb0f689..4fe7330120 100644
--- a/articles/quickstart/backend/rails/01-authorization.md
+++ b/articles/quickstart/backend/rails/01-authorization.md
@@ -21,7 +21,7 @@ useCase: quickstart
### Install dependencies
-This tutorial performs access token validation using the **jwt** Gem within a custom `Auth0Client` class. A Concern called `Secured` is used to authorize endpoints which require authentication through an incoming access token.
+This tutorial performs access token validation using the **jwt** Gem within a custom `Auth0Client` class. A Concern called `Secured` is used to authorize endpoints which require authentication through an incoming access token.
Install the **jwt** Gem.
diff --git a/articles/quickstart/backend/rails/interactive.md b/articles/quickstart/backend/rails/interactive.md
index 9439797da1..93069f4e7b 100644
--- a/articles/quickstart/backend/rails/interactive.md
+++ b/articles/quickstart/backend/rails/interactive.md
@@ -20,7 +20,7 @@ files:
# Add Authorization to Your Ruby on Rails API
-This tutorial performs access token validation using the **jwt** Gem within a custom `Auth0Client` class. A Concern called `Secured` is used to authorize endpoints which require authentication through an incoming access token.
+This tutorial performs access token validation using the **jwt** Gem within a custom `Auth0Client` class. A Concern called `Secured` is used to authorize endpoints which require authentication through an incoming access token.
If you have not created an API in your Auth0 dashboard yet, use the interactive selector to create a new Auth0 API or select an existing API for your project.
diff --git a/articles/quickstart/native/_includes/_authorization-create-rule.md b/articles/quickstart/native/_includes/_authorization-create-rule.md
index 63e8f760b1..f38269aab2 100644
--- a/articles/quickstart/native/_includes/_authorization-create-rule.md
+++ b/articles/quickstart/native/_includes/_authorization-create-rule.md
@@ -1,4 +1,4 @@
-First, you will create a rule that assigns users to either an `admin` role, or a single `user` role. Go to the New Rule page on the Auth0 dashboard and select the **Set Roles To A User** template, under **Access Control**.
+First, you will create a rule that assigns users to either an `admin` role, or a single `user` role. Go to the New Rule page on the Auth0 dashboard and select the **Set Roles To A User** template, under **Access Control**.
By default, this rule will assign the user an `admin` role if their email contains `@example.com`. Otherwise, they will be assigned a regular `user` role.
diff --git a/articles/quickstart/native/_includes/_authorization-introduction.md b/articles/quickstart/native/_includes/_authorization-introduction.md
index ea7e4e79bd..3217218555 100644
--- a/articles/quickstart/native/_includes/_authorization-introduction.md
+++ b/articles/quickstart/native/_includes/_authorization-introduction.md
@@ -1,5 +1,5 @@
Many identity providers will supply access claims, like roles or groups, with the user. You can request these in the token by setting `scope: openid roles` or `scope: openid groups`. However, not every identity provider supplies this type of information. Fortunately, Auth0 has an alternative, which is to create a rule for assigning different roles to different users.
::: note
-This tutorial assumes that you have already completed the rules tutorial and that you know how to implement a basic rule in your app.
+This tutorial assumes that you have already completed the rules tutorial and that you know how to implement a basic rule in your app.
:::
diff --git a/articles/quickstart/native/_includes/_callback-url-introduction.md b/articles/quickstart/native/_includes/_callback-url-introduction.md
index 1f4b495025..bf60aabc9c 100644
--- a/articles/quickstart/native/_includes/_callback-url-introduction.md
+++ b/articles/quickstart/native/_includes/_callback-url-introduction.md
@@ -2,7 +2,7 @@
A callback URL is a URL in your application where Auth0 redirects the user after they have been authenticated. Auth0 adds parameters to the callback URL, including a token.
-Callback URLs can be manipulated by attackers. For security, add your application's URL to the **Allowed Callback URLs** field in your Application Settings.
+Callback URLs can be manipulated by attackers. For security, add your application's URL to the **Allowed Callback URLs** field in your Application Settings.
If you do not add your application's URL to the list of Allowed Callback URLs, your users will see a mismatch error when they try to log in.
diff --git a/articles/quickstart/native/_includes/_calling_api_create_api.md b/articles/quickstart/native/_includes/_calling_api_create_api.md
index cf1f1b7567..08a59ee1be 100644
--- a/articles/quickstart/native/_includes/_calling_api_create_api.md
+++ b/articles/quickstart/native/_includes/_calling_api_create_api.md
@@ -1,6 +1,6 @@
## Create an Auth0 API
-In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API.
+In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API.
You will use the identifier later when you're preparing the Web Authentication.
For **Signing Algorithm**, select **RS256**.
diff --git a/articles/quickstart/native/_includes/_calling_api_create_scope.md b/articles/quickstart/native/_includes/_calling_api_create_scope.md
index ba63720498..87f0601743 100644
--- a/articles/quickstart/native/_includes/_calling_api_create_scope.md
+++ b/articles/quickstart/native/_includes/_calling_api_create_scope.md
@@ -2,7 +2,7 @@
By default, the Access Token does not contain any authorization information. To limit access to your resources based on authorization, you must use scopes. Read more about scopes in the scopes documentation.
-In the Auth0 dashboard, in the APIs section, click **Scopes**. Add any scopes you need to limit access to your API resources.
+In the Auth0 dashboard, in the APIs section, click **Scopes**. Add any scopes you need to limit access to your API resources.
::: note
You can give any names to your scopes. A common pattern is `:`. The example below uses the name `read:messages` for a scope.
diff --git a/articles/quickstart/native/_includes/_create_application.md b/articles/quickstart/native/_includes/_create_application.md
index 12abb794b3..d3ab5a20cf 100644
--- a/articles/quickstart/native/_includes/_create_application.md
+++ b/articles/quickstart/native/_includes/_create_application.md
@@ -1,3 +1,3 @@
## Create an application
-Create a new application in your Auth0 dashboard. For **Type**, select **Native**.
\ No newline at end of file
+Create a new application in your Auth0 dashboard. For **Type**, select **Native**.
\ No newline at end of file
diff --git a/articles/quickstart/native/_includes/_ios_config.md b/articles/quickstart/native/_includes/_ios_config.md
index 887f008dda..77794bc15d 100644
--- a/articles/quickstart/native/_includes/_ios_config.md
+++ b/articles/quickstart/native/_includes/_ios_config.md
@@ -2,7 +2,7 @@
## Add Auth0 Credentials
-You will need some details about this application to communicate with Auth0. You can get these details from the Application Settings in the Auth0 dashboard.
+You will need some details about this application to communicate with Auth0. You can get these details from the Application Settings in the Auth0 dashboard.
You need the following information:
* **Client ID**
@@ -55,7 +55,7 @@ In your application's `Info.plist` file, register your iOS Bundle identifier as
If your `Info.plist` file is not in the format shown above, you can right-click `Info.plist` in Xcode and select **Open As** > **Source Code**.
:::
-Go to your Dashboard Settings and make sure that the **Allowed Callback URLs** field contains the following callback URL:
+Go to your Dashboard Settings and make sure that the **Allowed Callback URLs** field contains the following callback URL:
```text
{PRODUCT_BUNDLE_IDENTIFIER}://${account.namespace}/ios/{PRODUCT_BUNDLE_IDENTIFIER}/callback
diff --git a/articles/quickstart/native/_includes/_rules-create-section.md b/articles/quickstart/native/_includes/_rules-create-section.md
index 1c676aed51..3fee4301ed 100644
--- a/articles/quickstart/native/_includes/_rules-create-section.md
+++ b/articles/quickstart/native/_includes/_rules-create-section.md
@@ -1,4 +1,4 @@
-To create a rule, go to the New Rule page. You can create a rule from scratch by selecting an empty rule, or use one of the existing templates. These templates are written by Auth0 to assist you to in executing common tasks.
+To create a rule, go to the New Rule page. You can create a rule from scratch by selecting an empty rule, or use one of the existing templates. These templates are written by Auth0 to assist you to in executing common tasks.
For this example, select the **Add country to the user profile** rule.
diff --git a/articles/quickstart/native/_includes/_rules-test-result-intro.md b/articles/quickstart/native/_includes/_rules-test-result-intro.md
index f5e201d4f0..1d5eb9010a 100644
--- a/articles/quickstart/native/_includes/_rules-test-result-intro.md
+++ b/articles/quickstart/native/_includes/_rules-test-result-intro.md
@@ -1,3 +1,3 @@
-To see the results of a created rule, login and fetch user profile information as explained in the User Profile step.
+To see the results of a created rule, login and fetch user profile information as explained in the User Profile step.
Then you can display the user profile's new `country` attribute added by the rule:
\ No newline at end of file
diff --git a/articles/quickstart/native/_includes/ionic/_configure_urls.md b/articles/quickstart/native/_includes/ionic/_configure_urls.md
index b0a51df7bf..327ed16b39 100644
--- a/articles/quickstart/native/_includes/ionic/_configure_urls.md
+++ b/articles/quickstart/native/_includes/ionic/_configure_urls.md
@@ -6,7 +6,7 @@
Throughout this article, `YOUR_PACKAGE_ID` is your application's package ID. This can be found and configured in the `appId` field in your `capacitor.config.ts` file. See Capacitors Config schema for more info.
:::
-Go to the Application Settings section in your Auth0 dashboard and set your **Callback URL** in the **Allowed Callback URLs** box.
+Go to the Application Settings section in your Auth0 dashboard and set your **Callback URL** in the **Allowed Callback URLs** box.
You should set the **Allowed Callback URL** to:
@@ -24,7 +24,7 @@ YOUR_PACKAGE_ID://${account.namespace}/capacitor/YOUR_PACKAGE_ID/callback
### Configure Origins
-To be able to make requests from your application to Auth0, set the following **Allowed Origins** in your Application Settings.
+To be able to make requests from your application to Auth0, set the following **Allowed Origins** in your Application Settings.
```bash
capacitor://localhost, http://localhost
@@ -32,4 +32,4 @@ capacitor://localhost, http://localhost
These origins are required for iOS and Android respectively.
-Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
\ No newline at end of file
+Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
\ No newline at end of file
diff --git a/articles/quickstart/native/_includes/ionic/_configure_urls_interactive.md b/articles/quickstart/native/_includes/ionic/_configure_urls_interactive.md
index 58b8272ac3..a61c78f9b2 100644
--- a/articles/quickstart/native/_includes/ionic/_configure_urls_interactive.md
+++ b/articles/quickstart/native/_includes/ionic/_configure_urls_interactive.md
@@ -34,10 +34,10 @@ If you are following along with our sample project, set this to `YOUR_PACKAGE_ID
### Configure Allowed Origins
-To be able to make requests from your native application to Auth0, set the following **Allowed Origins** in your Application Settings.
+To be able to make requests from your native application to Auth0, set the following **Allowed Origins** in your Application Settings.
::: note
If you are following along with our sample project, set this to `capacitor://localhost, http://localhost` for iOS and Android respectively.
:::
-Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
+Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
diff --git a/articles/quickstart/native/android/00-login.md b/articles/quickstart/native/android/00-login.md
index 3f00af5e71..7bf426ff9c 100755
--- a/articles/quickstart/native/android/00-login.md
+++ b/articles/quickstart/native/android/00-login.md
@@ -59,7 +59,7 @@ android {
```
::: panel Sync Project with Gradle Files
-Remember to synchronize using the Android Studio prompt or run `./gradlew clean build` from the command line. For more information about Gradle usage, check their official documentation.
+Remember to synchronize using the Android Studio prompt or run `./gradlew clean build` from the command line. For more information about Gradle usage, check their official documentation.
:::
Add manifest placeholders required by the SDK. The placeholders are used internally to define an `intent-filter` that captures the authentication callback URL. For this, the Auth0 tenant domain and the scheme that take part in the callback URL must be set.
@@ -136,7 +136,7 @@ class MainActivity : AppCompatActivity() {
We suggest you do not hardcode the values for `clientId` and `domain` as you may need to change them in the future. Instead, use String Resources, such as `@string/com_auth0_domain`, to define the values.
:::
-Finally, create a `loginWithBrowser` method and use the `WebAuthProvider` class to authenticate with any connection you enabled on your application in the Auth0 dashboard. Here, you can pass the scheme value that was used in the `auth0Scheme` manifest placeholder as part of the initial configuration:
+Finally, create a `loginWithBrowser` method and use the `WebAuthProvider` class to authenticate with any connection you enabled on your application in the Auth0 dashboard. Here, you can pass the scheme value that was used in the `auth0Scheme` manifest placeholder as part of the initial configuration:
```kotlin
private fun loginWithBrowser() {
diff --git a/articles/quickstart/native/android/download.md b/articles/quickstart/native/android/download.md
index 7cfbddbebc..51f51bd5bd 100644
--- a/articles/quickstart/native/android/download.md
+++ b/articles/quickstart/native/android/download.md
@@ -1,12 +1,12 @@
-To run the sample first set the **Callback URL** in the Application Settings to
+To run the sample first set the **Callback URL** in the Application Settings to
```text
demo://${account.namespace}/android/com.auth0.androidsample/callback
```
-To run the sample first set the **Logout URL** in the Application Settings to
+To run the sample first set the **Logout URL** in the Application Settings to
```text
demo://${account.namespace}/android/com.auth0.androidsample/callback
diff --git a/articles/quickstart/native/android/interactive.md b/articles/quickstart/native/android/interactive.md
index 3397f98dcc..5969faffc2 100644
--- a/articles/quickstart/native/android/interactive.md
+++ b/articles/quickstart/native/android/interactive.md
@@ -91,7 +91,7 @@ For more information about using Gradle, check the Auth0 dashboard. Here, you can pass the scheme value that was used in the `auth0Scheme` manifest placeholder as part of the initial configuration.
+Create a `loginWithBrowser` method and use the `WebAuthProvider` class to authenticate with any connection you enabled on your application in the Auth0 dashboard. Here, you can pass the scheme value that was used in the `auth0Scheme` manifest placeholder as part of the initial configuration.
After you call the `WebAuthProvider#start` function, the browser launches and shows the login page. Once the user authenticates, the callback URL is called. The callback URL contains the final result of the authentication process.
diff --git a/articles/quickstart/native/flutter/01-login.md b/articles/quickstart/native/flutter/01-login.md
index bb8eed8e64..8971094be3 100644
--- a/articles/quickstart/native/flutter/01-login.md
+++ b/articles/quickstart/native/flutter/01-login.md
@@ -43,7 +43,7 @@ The callback and logout URLs are the URLs that Auth0 invokes to redirect back to
If the callback and logout URLs are not set, users will be unable to log in and out of the app and will get an error.
-Go to the settings page of your Auth0 application and add the following URLs to **Allowed Callback URLs** and **Allowed Logout URLs**, depending on the platform of your app. If you have a custom domain, use this instead of the Auth0 domain from the settings page.
+Go to the settings page of your Auth0 application and add the following URLs to **Allowed Callback URLs** and **Allowed Logout URLs**, depending on the platform of your app. If you have a custom domain, use this instead of the Auth0 domain from the settings page.
::: note
On Android, the value of the `SCHEME` placeholder can be `https` or some other custom scheme. `https` schemes require enabling Android App Links.
@@ -131,7 +131,7 @@ This step requires a paid Apple Developer account. It is needed to use Universal
#### Configure the Team ID and bundle identifier
-Go to the settings page of your Auth0 application, scroll to the end, and open **Advanced Settings > Device Settings**. In the **iOS** section, set **Team ID** to your Apple Team ID, and **App ID** to your app's bundle identifier.
+Go to the settings page of your Auth0 application, scroll to the end, and open **Advanced Settings > Device Settings**. In the **iOS** section, set **Team ID** to your Apple Team ID, and **App ID** to your app's bundle identifier.

diff --git a/articles/quickstart/native/flutter/index.yml b/articles/quickstart/native/flutter/index.yml
index c09ff74e18..23ca3922c3 100644
--- a/articles/quickstart/native/flutter/index.yml
+++ b/articles/quickstart/native/flutter/index.yml
@@ -39,7 +39,7 @@ requirements:
- iOS 13+ and Xcode 14+ (for iOS)
- macOS 11+ and Xcode 14+ (for macOS)
next_steps:
- - path: interactive
+ - path: 01-login
list:
- text: Configure other identity providers
icon: 345
diff --git a/articles/quickstart/native/flutter/interactive.md b/articles/quickstart/native/flutter/interactive.md
index c32f9e1423..99d622f8f2 100644
--- a/articles/quickstart/native/flutter/interactive.md
+++ b/articles/quickstart/native/flutter/interactive.md
@@ -71,7 +71,7 @@ This step requires a paid Apple Developer account. It is needed to use Universal
### Configure the Team ID and bundle identifier
-Go to the settings page of your Auth0 application, scroll to the end, and open **Advanced Settings > Device Settings**. In the **iOS** section, set **Team ID** to your Apple Team ID, and **App ID** to your app's bundle identifier.
+Go to the settings page of your Auth0 application, scroll to the end, and open **Advanced Settings > Device Settings**. In the **iOS** section, set **Team ID** to your Apple Team ID, and **App ID** to your app's bundle identifier.

diff --git a/articles/quickstart/native/ionic-angular/01-login.md b/articles/quickstart/native/ionic-angular/01-login.md
index 161b8f7388..b93e0379de 100644
--- a/articles/quickstart/native/ionic-angular/01-login.md
+++ b/articles/quickstart/native/ionic-angular/01-login.md
@@ -71,7 +71,7 @@ const redirect_uri = `<%= "${config.appId}" %>://${account.namespace}/capacitor/
The `AuthModule.forRoot` function takes the following configuration:
-- `domain`: The "domain" value present under the "Settings" of the application you created in your Auth0 dashboard, or your custom domain if using Auth0's Custom Domains feature
+- `domain`: The "domain" value present under the "Settings" of the application you created in your Auth0 dashboard, or your custom domain if using Auth0's Custom Domains feature
- `clientId`: The "client ID" value present under the "Settings" of the application you created in your Auth0 dashboard
- `useRefreshTokens`: To use auth0-angular with Ionic on Android and iOS, it's required to enable refresh tokens.
- `useRefreshTokensFallback`: To use auth0-angular with Ionic on Android and iOS, it's required to disable the iframe fallback.
diff --git a/articles/quickstart/native/ionic-angular/download.md b/articles/quickstart/native/ionic-angular/download.md
index b036c2fc41..3d1147320c 100644
--- a/articles/quickstart/native/ionic-angular/download.md
+++ b/articles/quickstart/native/ionic-angular/download.md
@@ -2,19 +2,19 @@
To run the sample follow these steps:
-1) Add the following URL to **Allowed Callback URLs** in the Application Settings
+1) Add the following URL to **Allowed Callback URLs** in the Application Settings
```text
com.auth0.samples://${account.namespace}/capacitor/com.auth0.samples/callback
```
-2) Add the following URL to **Allowed Logout URLs** in the Application Settings
+2) Add the following URL to **Allowed Logout URLs** in the Application Settings
```text
com.auth0.samples://${account.namespace}/capacitor/com.auth0.samples/callback
```
-3) Add the following to **Allowed Origins (CORS)** in the Application Settings
+3) Add the following to **Allowed Origins (CORS)** in the Application Settings
```text
capacitor://localhost, http://localhost
diff --git a/articles/quickstart/native/ionic-angular/interactive.md b/articles/quickstart/native/ionic-angular/interactive.md
index 1b45676b3e..463c683893 100644
--- a/articles/quickstart/native/ionic-angular/interactive.md
+++ b/articles/quickstart/native/ionic-angular/interactive.md
@@ -40,7 +40,7 @@ The SDK exports `AuthModule`, a module that contains all the services required f
The `AuthModule.forRoot` function takes the following configuration:
-- `domain`: The `domain` value present under the **Settings** of the application you created in the Auth0 Dashboard, or your custom domain if you are using Auth0's custom domains feature.
+- `domain`: The `domain` value present under the **Settings** of the application you created in the Auth0 Dashboard, or your custom domain if you are using Auth0's custom domains feature.
- `clientId`: The Client ID value present under the **Settings** of the application you created in the Auth0 Dashboard.
- `useRefreshTokens`: To use auth0-angular with Ionic on Android and iOS, it's required to enable refresh tokens.
- `useRefreshTokensFallback`: To use auth0-angular with Ionic on Android and iOS, it's required to disable the iframe fallback.
diff --git a/articles/quickstart/native/ionic-react/01-login.md b/articles/quickstart/native/ionic-react/01-login.md
index 9f08b9648c..1ec92b5d60 100644
--- a/articles/quickstart/native/ionic-react/01-login.md
+++ b/articles/quickstart/native/ionic-react/01-login.md
@@ -58,7 +58,7 @@ root.render(
The `Auth0Provider` component takes the following props:
-- `domain`: The "domain" value present under the "Settings" of the application you created in your Auth0 dashboard, or your custom domain if using Auth0's Custom Domains feature
+- `domain`: The "domain" value present under the "Settings" of the application you created in your Auth0 dashboard, or your custom domain if using Auth0's Custom Domains feature
- `clientId`: The "client ID" value present under the "Settings" of the application you created in your Auth0 dashboard
- `useRefreshTokens`: To use auth0-react with Ionic on Android and iOS, it's required to enable refresh tokens.
- `useRefreshTokensFallback`: To use auth0-react with Ionic on Android and iOS, it's required to disable the iframe fallback.
diff --git a/articles/quickstart/native/ionic-react/download.md b/articles/quickstart/native/ionic-react/download.md
index f5e15386e8..6dd3a8e492 100644
--- a/articles/quickstart/native/ionic-react/download.md
+++ b/articles/quickstart/native/ionic-react/download.md
@@ -2,19 +2,19 @@
To run the sample follow these steps:
-1) Add the following URL to **Allowed Callback URLs** in the Application Settings
+1) Add the following URL to **Allowed Callback URLs** in the Application Settings
```text
com.auth0.samples://${account.namespace}/capacitor/com.auth0.samples/callback
```
-2) Add the following URL to **Allowed Logout URLs** in the Application Settings
+2) Add the following URL to **Allowed Logout URLs** in the Application Settings
```text
com.auth0.samples://${account.namespace}/capacitor/com.auth0.samples/callback
```
-3) Add the following to **Allowed Origins (CORS)s** in the Application Settings
+3) Add the following to **Allowed Origins (CORS)s** in the Application Settings
```text
capacitor://localhost, http://localhost
diff --git a/articles/quickstart/native/ionic-react/interactive.md b/articles/quickstart/native/ionic-react/interactive.md
index 1cab236a4e..a92859a39b 100644
--- a/articles/quickstart/native/ionic-react/interactive.md
+++ b/articles/quickstart/native/ionic-react/interactive.md
@@ -36,11 +36,11 @@ Auth0 allows you to quickly add authentication and gain access to user profile i
## Configure the `Auth0Provider` component {{{ data-action=code data-code="index.tsx" }}}
-Under the hood, the Auth0 React SDK uses React Context to manage the authentication state of your users. One way to integrate Auth0 with your React app is to wrap your root component with an `Auth0Provider` you can import from the SDK.
+Under the hood, the Auth0 React SDK uses React Context to manage the authentication state of your users. One way to integrate Auth0 with your React app is to wrap your root component with an `Auth0Provider` you can import from the SDK.
The `Auth0Provider` component takes the following props:
-- `domain`: The `domain` value present under the **Settings** of the application you created in your Auth0 Dashboard, or your custom domain if using Auth0's Custom Domains feature.
+- `domain`: The `domain` value present under the **Settings** of the application you created in your Auth0 Dashboard, or your custom domain if using Auth0's Custom Domains feature.
- `clientId`: The Client ID value present under the **Settings** of the application you created in your Auth0 Dashboard.
- `useRefreshTokens`: To use auth0-react with Ionic on Android and iOS, it's required to enable refresh tokens.
- `useRefreshTokensFallback`: To use auth0-react with Ionic on Android and iOS, it's required to disable the iframe fallback.
diff --git a/articles/quickstart/native/ionic-vue/01-login.md b/articles/quickstart/native/ionic-vue/01-login.md
index 4177796679..0e31f36580 100644
--- a/articles/quickstart/native/ionic-vue/01-login.md
+++ b/articles/quickstart/native/ionic-vue/01-login.md
@@ -69,7 +69,7 @@ router.isReady().then(() => {
The `createAuth0` plugin takes the following props:
-- `domain`: The "domain" value present under the "Settings" of the application you created in your Auth0 dashboard, or your custom domain if using Auth0's Custom Domains feature
+- `domain`: The "domain" value present under the "Settings" of the application you created in your Auth0 dashboard, or your custom domain if using Auth0's Custom Domains feature
- `clientId`: The "client ID" value present under the "Settings" of the application you created in your Auth0 dashboard
- `useRefreshTokens`: To use auth0-vue with Ionic on Android and iOS, it's required to enable refresh tokens.
- `useRefreshTokensFallback`: To use auth0-vue with Ionic on Android and iOS, it's required to disable the iframe fallback.
diff --git a/articles/quickstart/native/ionic-vue/download.md b/articles/quickstart/native/ionic-vue/download.md
index 9d0a391968..58a0397ae6 100644
--- a/articles/quickstart/native/ionic-vue/download.md
+++ b/articles/quickstart/native/ionic-vue/download.md
@@ -2,19 +2,19 @@
To run the sample follow these steps:
-1) Add the following URL to **Allowed Callback URLs** in the Application Settings
+1) Add the following URL to **Allowed Callback URLs** in the Application Settings
```text
com.auth0.samples://${account.namespace}/capacitor/com.auth0.samples/callback
```
-2) Add the following URL to **Allowed Logout URLs** in the Application Settings
+2) Add the following URL to **Allowed Logout URLs** in the Application Settings
```text
com.auth0.samples://${account.namespace}/capacitor/com.auth0.samples/callback
```
-3) Add the following to **Allowed Origins (CORS)s** in the Application Settings
+3) Add the following to **Allowed Origins (CORS)s** in the Application Settings
```text
capacitor://localhost, http://localhost
diff --git a/articles/quickstart/native/ionic-vue/interactive.md b/articles/quickstart/native/ionic-vue/interactive.md
index 4f6df0fae6..28601bb055 100644
--- a/articles/quickstart/native/ionic-vue/interactive.md
+++ b/articles/quickstart/native/ionic-vue/interactive.md
@@ -40,7 +40,7 @@ The SDK exports `createAuth0`, a composable that contains all the services requi
The `createAuth0` composable takes the following configuration:
-- `domain`: The `domain` value present under the **Settings** of the application you created in the Auth0 Dashboard, or your custom domain if you are using Auth0's custom domains feature.
+- `domain`: The `domain` value present under the **Settings** of the application you created in the Auth0 Dashboard, or your custom domain if you are using Auth0's custom domains feature.
- `clientId`: The Client ID value present under the **Settings** of the application you created in the Auth0 Dashboard.
- `useRefreshTokens`: To use auth0-vue with Ionic on Android and iOS, it's required to enable refresh tokens.
- `useRefreshTokensFallback`: To use auth0-vue with Ionic on Android and iOS, it's required to disable the iframe fallback.
diff --git a/articles/quickstart/native/ios-swift/01-login.md b/articles/quickstart/native/ios-swift/01-login.md
index c215fa5eb6..0998ae00ea 100755
--- a/articles/quickstart/native/ios-swift/01-login.md
+++ b/articles/quickstart/native/ios-swift/01-login.md
@@ -33,7 +33,7 @@ On iOS 17.4+ and macOS 14.4+ it is possible to use Universal Links as callback a
**This feature requires Xcode 15.3+ and a paid Apple Developer account**.
:::
-Go to the settings page of your Auth0 application and add the following URLs to **Allowed Callback URLs** and **Allowed Logout URLs**, depending on the platform of your app. If you have a custom domain, use this instead of the value from the settings page.
+Go to the settings page of your Auth0 application and add the following URLs to **Allowed Callback URLs** and **Allowed Logout URLs**, depending on the platform of your app. If you have a custom domain, use this instead of the value from the settings page.
#### iOS
@@ -140,7 +140,7 @@ For further reference on Carthage, check their settings page of your Auth0 application. If you are using a custom domain, use the value of your custom domain instead of the value from the settings page.
+The Auth0.swift SDK needs the **Client ID** and **domain** of the Auth0 application to communicate with Auth0. You can find these details in the settings page of your Auth0 application. If you are using a custom domain, use the value of your custom domain instead of the value from the settings page.
<% if(typeof hideDashboardScreenshot === 'undefined' || hideDashboardScreenshot !== true) { %>

diff --git a/articles/quickstart/native/ios-swift/interactive.md b/articles/quickstart/native/ios-swift/interactive.md
index ae718e28d3..cfd875ae1a 100644
--- a/articles/quickstart/native/ios-swift/interactive.md
+++ b/articles/quickstart/native/ios-swift/interactive.md
@@ -82,7 +82,7 @@ This step requires a paid Apple Developer account. It is needed to use Universal
#### Configure the Team ID and bundle identifier
-Go to the settings page of your Auth0 application, scroll to the end, and open **Advanced Settings > Device Settings**. In the **iOS** section, set **Team ID** to your Apple Team ID, and **App ID** to your app's bundle identifier.
+Go to the settings page of your Auth0 application, scroll to the end, and open **Advanced Settings > Device Settings**. In the **iOS** section, set **Team ID** to your Apple Team ID, and **App ID** to your app's bundle identifier.

@@ -156,7 +156,7 @@ For further reference on Carthage, check their settings page of your Auth0 application.
+The Auth0.swift SDK needs your Auth0 **domain** and **Client ID**. You can find these values in the settings page of your Auth0 application.
- **domain**: The domain of your Auth0 tenant. If you have a custom domain, use this instead of your Auth0 tenant’s domain.
- **Client ID**: The alphanumeric, unique ID of the Auth0 application you set up earlier in this quickstart.
diff --git a/articles/quickstart/native/maui/download.md b/articles/quickstart/native/maui/download.md
index 916a47fdb5..96bd62f994 100644
--- a/articles/quickstart/native/maui/download.md
+++ b/articles/quickstart/native/maui/download.md
@@ -1,10 +1,10 @@
-To run the sample first set the **Allowed Callback URLs** in the Application Settings:
+To run the sample first set the **Allowed Callback URLs** in the Application Settings:
```text
myapp://callback
```
-Set the **Allowed Logout URLs** in the Application Settings:
+Set the **Allowed Logout URLs** in the Application Settings:
```text
myapp://callback
diff --git a/articles/quickstart/native/net-android-ios/01-login.md b/articles/quickstart/native/net-android-ios/01-login.md
index b575f9d5c1..c404a03cbf 100755
--- a/articles/quickstart/native/net-android-ios/01-login.md
+++ b/articles/quickstart/native/net-android-ios/01-login.md
@@ -190,7 +190,7 @@ if (!loginResult.IsError)
### Obtaining the User Information
-On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.aspx).
+On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.
To obtain information about the user, you can query the claims. You can, for example, obtain the user's name and email address from the `name` and `email` claims:
diff --git a/articles/quickstart/native/net-android-ios/_configure_urls_interactive.md b/articles/quickstart/native/net-android-ios/_configure_urls_interactive.md
index e80b9d3118..755e7c5a89 100644
--- a/articles/quickstart/native/net-android-ios/_configure_urls_interactive.md
+++ b/articles/quickstart/native/net-android-ios/_configure_urls_interactive.md
@@ -34,4 +34,4 @@ If you are following along with our sample project, set this to one of the follo
**iOS**: `YOUR_BUNDLE_ID://${account.namespace}/ios/YOUR_BUNDLE_ID/callback`
:::
-Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
+Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
diff --git a/articles/quickstart/native/net-android-ios/download.md b/articles/quickstart/native/net-android-ios/download.md
index d680bc82ee..4aea81c06c 100644
--- a/articles/quickstart/native/net-android-ios/download.md
+++ b/articles/quickstart/native/net-android-ios/download.md
@@ -1,10 +1,10 @@
-To run the sample first set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
+To run the sample first set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0.quickstart://${account.namespace}/android/com.auth0.quickstart/callback com.auth0.iossample://${account.namespace}/ios/com.auth0.iossample/callback
```
-Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
+Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0.quickstart://${account.namespace}/android/com.auth0.quickstart/callback com.auth0.iossample://${account.namespace}/ios/com.auth0.iossample/callback
diff --git a/articles/quickstart/native/react-native-expo/00-login.md b/articles/quickstart/native/react-native-expo/00-login.md
index 5ac6c024cb..88024c27ac 100644
--- a/articles/quickstart/native/react-native-expo/00-login.md
+++ b/articles/quickstart/native/react-native-expo/00-login.md
@@ -111,7 +111,7 @@ The callback and logout URLs are the URLs that Auth0 invokes to redirect back to
If the callback and logout URLs are not set, users will be unable to log in and out of the application and will get an error.
-Go to the settings page of your Auth0 application and add the corresponding URL to **Allowed Callback URLs** and **Allowed Logout URLs**, according to the platform of your application. If you are using a custom domain, use the value of your custom domain instead of the Auth0 domain from the settings page.
+Go to the settings page of your Auth0 application and add the corresponding URL to **Allowed Callback URLs** and **Allowed Logout URLs**, according to the platform of your application. If you are using a custom domain, use the value of your custom domain instead of the Auth0 domain from the settings page.
#### iOS
```text
diff --git a/articles/quickstart/native/react-native-expo/download.md b/articles/quickstart/native/react-native-expo/download.md
index 4b885ae27d..cb1fd28418 100644
--- a/articles/quickstart/native/react-native-expo/download.md
+++ b/articles/quickstart/native/react-native-expo/download.md
@@ -1,11 +1,11 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
+1) Set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0samples://${account.namespace}/ios/com.auth0samples/callback,com.auth0samples://${account.namespace}/android/com.auth0samples/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
+2) Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0samples://${account.namespace}/ios/com.auth0samples/callback,com.auth0samples://${account.namespace}/android/com.auth0samples/callback
```
diff --git a/articles/quickstart/native/react-native/00-login.md b/articles/quickstart/native/react-native/00-login.md
index b4a7b3b89c..325a8f6ff2 100644
--- a/articles/quickstart/native/react-native/00-login.md
+++ b/articles/quickstart/native/react-native/00-login.md
@@ -147,7 +147,7 @@ The callback and logout URLs are the URLs that Auth0 invokes to redirect back to
If the callback and logout URLs are not set, users will be unable to log in and out of the application and will get an error.
-Go to the settings page of your Auth0 application and add the corresponding URL to **Allowed Callback URLs** and **Allowed Logout URLs**, according to the platform of your application. If you are using a custom domain, use the value of your custom domain instead of the Auth0 domain from the settings page.
+Go to the settings page of your Auth0 application and add the corresponding URL to **Allowed Callback URLs** and **Allowed Logout URLs**, according to the platform of your application. If you are using a custom domain, use the value of your custom domain instead of the Auth0 domain from the settings page.
#### iOS
```text
diff --git a/articles/quickstart/native/react-native/download.md b/articles/quickstart/native/react-native/download.md
index 62e4538c19..fcd746a690 100644
--- a/articles/quickstart/native/react-native/download.md
+++ b/articles/quickstart/native/react-native/download.md
@@ -1,11 +1,11 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
+1) Set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0samples://${account.namespace}/ios/com.auth0samples/callback,com.auth0samples://${account.namespace}/android/com.auth0samples/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
+2) Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0samples://${account.namespace}/ios/com.auth0samples/callback,com.auth0samples://${account.namespace}/android/com.auth0samples/callback
```
diff --git a/articles/quickstart/native/react-native/interactive.md b/articles/quickstart/native/react-native/interactive.md
index fb373f00be..2f1c0e16fa 100644
--- a/articles/quickstart/native/react-native/interactive.md
+++ b/articles/quickstart/native/react-native/interactive.md
@@ -101,7 +101,7 @@ First, you must provide a way for your users to log in. We recommend using the A
### Configure Android
-Open the `build.gradle` file in your application directory (typically at `android/app/build.gradle`) and add the following manifest placeholders. The value for `auth0Domain` should contain your Auth0 application settings as configured above.
+Open the `build.gradle` file in your application directory (typically at `android/app/build.gradle`) and add the following manifest placeholders. The value for `auth0Domain` should contain your Auth0 application settings [as configured above](#get-your-application-keys).
```groovy
android {
diff --git a/articles/quickstart/native/windows-uwp-csharp/01-login.md b/articles/quickstart/native/windows-uwp-csharp/01-login.md
index ac4a6f8242..058b719f99 100644
--- a/articles/quickstart/native/windows-uwp-csharp/01-login.md
+++ b/articles/quickstart/native/windows-uwp-csharp/01-login.md
@@ -78,7 +78,7 @@ if (!loginResult.IsError)
### Obtaining the User Information
-On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.aspx).
+On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.
To obtain information about the user, you can query the claims. You can for example obtain the user's name and email address from the `name` and `email` claims:
diff --git a/articles/quickstart/native/wpf-winforms/01-login.md b/articles/quickstart/native/wpf-winforms/01-login.md
index e8766307d3..2fd10b643f 100644
--- a/articles/quickstart/native/wpf-winforms/01-login.md
+++ b/articles/quickstart/native/wpf-winforms/01-login.md
@@ -82,7 +82,7 @@ if (!loginResult.IsError)
### Obtaining the User Information
-On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.aspx).
+On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.
To obtain information about the user, you can query the claims. You can for example obtain the user's name and email address from the `name` and `email` claims:
diff --git a/articles/quickstart/native/wpf-winforms/download.md b/articles/quickstart/native/wpf-winforms/download.md
index 55ee1cc0b1..89fb96b6e6 100644
--- a/articles/quickstart/native/wpf-winforms/download.md
+++ b/articles/quickstart/native/wpf-winforms/download.md
@@ -1,11 +1,11 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
https://${account.namespace}/mobile
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
https://${account.namespace}/mobile
```
diff --git a/articles/quickstart/native/xamarin/01-login.md b/articles/quickstart/native/xamarin/01-login.md
index c34e04c7d7..5da9ef65a9 100755
--- a/articles/quickstart/native/xamarin/01-login.md
+++ b/articles/quickstart/native/xamarin/01-login.md
@@ -183,7 +183,7 @@ if (!loginResult.IsError)
### Obtaining the User Information
-On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.aspx).
+On successful login, the login result will contain the user information in the `User` property, which is a ClaimsPrincipal.
To obtain information about the user, you can query the claims. You can, for example, obtain the user's name and email address from the `name` and `email` claims:
diff --git a/articles/quickstart/native/xamarin/_configure_urls_interactive.md b/articles/quickstart/native/xamarin/_configure_urls_interactive.md
index e80b9d3118..755e7c5a89 100644
--- a/articles/quickstart/native/xamarin/_configure_urls_interactive.md
+++ b/articles/quickstart/native/xamarin/_configure_urls_interactive.md
@@ -34,4 +34,4 @@ If you are following along with our sample project, set this to one of the follo
**iOS**: `YOUR_BUNDLE_ID://${account.namespace}/ios/YOUR_BUNDLE_ID/callback`
:::
-Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
+Lastly, be sure that the **Application Type** for your application is set to **Native** in the Application Settings.
diff --git a/articles/quickstart/native/xamarin/download.md b/articles/quickstart/native/xamarin/download.md
index d680bc82ee..4aea81c06c 100644
--- a/articles/quickstart/native/xamarin/download.md
+++ b/articles/quickstart/native/xamarin/download.md
@@ -1,10 +1,10 @@
-To run the sample first set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
+To run the sample first set the **Allowed Callback URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0.quickstart://${account.namespace}/android/com.auth0.quickstart/callback com.auth0.iossample://${account.namespace}/ios/com.auth0.iossample/callback
```
-Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
+Set the **Allowed Logout URLs** in the Application Settings so it works for both Android and iOS apps:
```text
com.auth0.quickstart://${account.namespace}/android/com.auth0.quickstart/callback com.auth0.iossample://${account.namespace}/ios/com.auth0.iossample/callback
diff --git a/articles/quickstart/spa/_includes/_authorization-create-rule.md b/articles/quickstart/spa/_includes/_authorization-create-rule.md
index 69c52a1322..e2f9b74f4a 100644
--- a/articles/quickstart/spa/_includes/_authorization-create-rule.md
+++ b/articles/quickstart/spa/_includes/_authorization-create-rule.md
@@ -1,4 +1,4 @@
-First, create a rule that assigns users to either an `admin` role or a single `user` role. Go to the New Rule page in the Auth0 dashboard and select the **Set Roles to a User** template under **Access Control**.
+First, create a rule that assigns users to either an `admin` role or a single `user` role. Go to the New Rule page in the Auth0 dashboard and select the **Set Roles to a User** template under **Access Control**.
By default, this rule will assign the user an `admin` role if the user’s email contains `@example.com`. Otherwise, the user will be assigned a regular `user` role.
diff --git a/articles/quickstart/spa/_includes/_authorization-introduction.md b/articles/quickstart/spa/_includes/_authorization-introduction.md
index c9c672ea1f..397a10870a 100644
--- a/articles/quickstart/spa/_includes/_authorization-introduction.md
+++ b/articles/quickstart/spa/_includes/_authorization-introduction.md
@@ -1,5 +1,5 @@
Many identity providers will supply access claims (such as roles or groups) with the user. You can request these in the token by setting `scope: openid roles` or `scope: openid groups`. However, not every identity provider supplies this type of information. Fortunately, Auth0 has an alternative, which is to create a rule for assigning different roles to different users.
::: note
-This tutorial assumes that you have already completed the rules tutorial and that you know how to implement a basic rule in your app.
+This tutorial assumes that you have already completed the rules tutorial and that you know how to implement a basic rule in your app.
:::
diff --git a/articles/quickstart/spa/_includes/_calling_api_create_api.md b/articles/quickstart/spa/_includes/_calling_api_create_api.md
index 02f899ebce..2a64c6f4e6 100644
--- a/articles/quickstart/spa/_includes/_calling_api_create_api.md
+++ b/articles/quickstart/spa/_includes/_calling_api_create_api.md
@@ -1,6 +1,6 @@
## Create an API
-In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API.
+In the APIs section of the Auth0 dashboard, click **Create API**. Provide a name and an identifier for your API.
You will use the identifier later when you're configuring your Javascript Auth0 application instance.
For **Signing Algorithm**, select **RS256**.
diff --git a/articles/quickstart/spa/_includes/_calling_api_create_scope.md b/articles/quickstart/spa/_includes/_calling_api_create_scope.md
index 62c2f7ea61..09f33fc218 100644
--- a/articles/quickstart/spa/_includes/_calling_api_create_scope.md
+++ b/articles/quickstart/spa/_includes/_calling_api_create_scope.md
@@ -2,7 +2,7 @@
By default, the Access Token does not contain any authorization information. To limit access to your resources based on authorization, you must use scopes. Read more about scopes in the scopes documentation.
-In the Auth0 dashboard, in the APIs section, click **Scopes**. Add any scopes you need to limit access to your API resources.
+In the Auth0 dashboard, in the APIs section, click **Scopes**. Add any scopes you need to limit access to your API resources.
::: note
You can give any names to your scopes. A common pattern is `:`. The example below uses the name `read:messages` for a scope.
diff --git a/articles/quickstart/spa/_includes/_calling_api_modify_backend.md b/articles/quickstart/spa/_includes/_calling_api_modify_backend.md
index 43535da58b..db9ae24c2c 100644
--- a/articles/quickstart/spa/_includes/_calling_api_modify_backend.md
+++ b/articles/quickstart/spa/_includes/_calling_api_modify_backend.md
@@ -33,7 +33,7 @@ app.get("/api/external", checkJwt, (req, res) => {
Notice that it continues to use the same `checkJwt` middleware in order to validate the Access Token. The difference here is that the Access Token must be validated using the API identifier, rather than the client ID that we used for the ID Token.
::: note
-The API identifier is the identifier that was specified when the API was created in the Auth0 dashboard.
+The API identifier is the identifier that was specified when the API was created in the Auth0 dashboard.
:::
Therefore, modify the `checkJwt` function to include the API identifier value in the `audience` setting:
diff --git a/articles/quickstart/spa/_includes/_login_preamble.md b/articles/quickstart/spa/_includes/_login_preamble.md
index cc27239338..1f00c7239c 100644
--- a/articles/quickstart/spa/_includes/_login_preamble.md
+++ b/articles/quickstart/spa/_includes/_login_preamble.md
@@ -5,7 +5,7 @@
::: note
You can also embed the login dialog directly in your application using the Lock widget. If you use this method, some features, such as single sign-on, will not be accessible.
<% if (typeof embeddedLoginLink == 'string') { %>
-To learn how to embed the Lock widget in your application, follow the Embedded Login sample.
+To learn how to embed the Lock widget in your application, follow the Embedded Login sample.
<% } %>
:::
diff --git a/articles/quickstart/spa/_includes/_rules-create-section.md b/articles/quickstart/spa/_includes/_rules-create-section.md
index dc5827d980..2fa1daf902 100644
--- a/articles/quickstart/spa/_includes/_rules-create-section.md
+++ b/articles/quickstart/spa/_includes/_rules-create-section.md
@@ -1,4 +1,4 @@
-To create a rule, go to the New Rule page. You can create a rule from scratch by selecting an empty rule, or you may use one of the existing templates. These templates are written by Auth0 to cover common scenarios and use cases.
+To create a rule, go to the New Rule page. You can create a rule from scratch by selecting an empty rule, or you may use one of the existing templates. These templates are written by Auth0 to cover common scenarios and use cases.
For this example, select the **Add country to the user profile** rule.
diff --git a/articles/quickstart/spa/_includes/_rules-test-result-intro.md b/articles/quickstart/spa/_includes/_rules-test-result-intro.md
index 4c23bc016e..c3a6a60d0e 100644
--- a/articles/quickstart/spa/_includes/_rules-test-result-intro.md
+++ b/articles/quickstart/spa/_includes/_rules-test-result-intro.md
@@ -1,3 +1,3 @@
-To see the results of a created rule, log in and fetch the user’s profile information, as explained in the User Profile step.
+To see the results of a created rule, log in and fetch the user’s profile information, as explained in the User Profile step.
Then you can display the user profile's new `country` attribute added by the rule:
diff --git a/articles/quickstart/spa/_includes/_silent-auth-social-idp.md b/articles/quickstart/spa/_includes/_silent-auth-social-idp.md
index 4ec041e598..ec59fd27db 100644
--- a/articles/quickstart/spa/_includes/_silent-auth-social-idp.md
+++ b/articles/quickstart/spa/_includes/_silent-auth-social-idp.md
@@ -2,7 +2,7 @@
Users who are logged in with **username/password** will be silently reauthenticated automatically when the application reloads. No further action is needed for this type of login.
-If you are using the classic Universal Login experience and would like users to authenticate using **social identity providers** (such as Google, Apple, Facebook, etc.), then you will need to configure those connections in your Auth0 Dashboard.
+If you are using the classic Universal Login experience and would like users to authenticate using **social identity providers** (such as Google, Apple, Facebook, etc.), then you will need to configure those connections in your Auth0 Dashboard.
In the navigation menu, choose **Connections** - **Social**, and select the social connection you’d like to support. In the connection’s settings, click “How to obtain a Client ID?“ and follow the instructions to set up your own ID and secret.
diff --git a/articles/quickstart/spa/_includes/_token_renewal_preamble.md b/articles/quickstart/spa/_includes/_token_renewal_preamble.md
index 63efb965e2..98d3d9d780 100644
--- a/articles/quickstart/spa/_includes/_token_renewal_preamble.md
+++ b/articles/quickstart/spa/_includes/_token_renewal_preamble.md
@@ -7,7 +7,7 @@ When you create an API in the Auth0 dashboard, the default expiry time for brows
This short expiry time is good for security, but can affect user experience. To improve user experience, provide a way for your users to automatically get a new Access Token and keep their client-side session alive. You can do this with Silent Authentication.
::: note
-You can control the expiry time of an Access Token from the APIs section.
-You can control the expiry time of an ID Token from the Applications section.
+You can control the expiry time of an Access Token from the APIs section.
+You can control the expiry time of an ID Token from the Applications section.
These settings are independent.
:::
\ No newline at end of file
diff --git a/articles/quickstart/spa/angular/01-login.md b/articles/quickstart/spa/angular/01-login.md
index 9dab2d079b..0dae8cafc8 100644
--- a/articles/quickstart/spa/angular/01-login.md
+++ b/articles/quickstart/spa/angular/01-login.md
@@ -120,7 +120,7 @@ export class AuthButtonComponent {
}
```
-Specify the `returnTo` option when calling `logout` to tell Auth0 where it should redirect to after a successful logout. This value must be specified in the **Allowed Logout URLs** setting in the dashboard.
+Specify the `returnTo` option when calling `logout` to tell Auth0 where it should redirect to after a successful logout. This value must be specified in the **Allowed Logout URLs** setting in the dashboard.
:::note
Here we use `http://localhost:4200` as the value for `logoutParams.returnTo`, but the associate sample uses `window.location.origin`, which in this case would resolve to the same value. Ultimately, this value should point to the root URL for your application.
diff --git a/articles/quickstart/spa/angular/download.md b/articles/quickstart/spa/angular/download.md
index b56790f3e8..a74d04f1ae 100644
--- a/articles/quickstart/spa/angular/download.md
+++ b/articles/quickstart/spa/angular/download.md
@@ -2,15 +2,15 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to
+1) Set the **Allowed Callback URLs** in the Application Settings to
```text
http://localhost:4200
```
-2) Set **Allowed Web Origins** in the Application Settings to
+2) Set **Allowed Web Origins** in the Application Settings to
```text
http://localhost:4200
```
-3) Set **Allowed Logout URLs** in the Application Settings to
+3) Set **Allowed Logout URLs** in the Application Settings to
```text
http://localhost:4200
```
diff --git a/articles/quickstart/spa/flutter/download.md b/articles/quickstart/spa/flutter/download.md
index f562781d7d..9d3470dc0c 100644
--- a/articles/quickstart/spa/flutter/download.md
+++ b/articles/quickstart/spa/flutter/download.md
@@ -2,7 +2,7 @@
To run the sample follow these steps:
-1. Set the **Allowed Callback URLs** and **Allowed Logout URLs** in the Application Settings to the following value so it works for both Android and iOS apps:
+1. Set the **Allowed Callback URLs** and **Allowed Logout URLs** in the Application Settings to the following value so it works for both Android and iOS apps:
```text
com.auth0.samples.FlutterSample://${account.namespace}/ios/com.auth0.samples.FlutterSample/callback,com.auth0.sample://${account.namespace}/android/com.auth0.sample/callback
diff --git a/articles/quickstart/spa/flutter/index.yml b/articles/quickstart/spa/flutter/index.yml
index 0b5b439218..d03c069e04 100644
--- a/articles/quickstart/spa/flutter/index.yml
+++ b/articles/quickstart/spa/flutter/index.yml
@@ -36,7 +36,7 @@ requirements:
- Xcode 14+ (for iOS)
- Android Studio 4+ (for Android)
next_steps:
- - path: interactive
+ - path: 01-login
list:
- text: Configure other identity providers
icon: 345
diff --git a/articles/quickstart/spa/react/01-login.md b/articles/quickstart/spa/react/01-login.md
index b959a34104..9c4223667a 100644
--- a/articles/quickstart/spa/react/01-login.md
+++ b/articles/quickstart/spa/react/01-login.md
@@ -24,7 +24,7 @@ Visit the React Context to manage the authentication state of your users. One way to integrate Auth0 with your React app is to wrap your root component with an `Auth0Provider` that you can import from the SDK.
+Under the hood, the Auth0 React SDK uses React Context to manage the authentication state of your users. One way to integrate Auth0 with your React app is to wrap your root component with an `Auth0Provider` that you can import from the SDK.
```javascript
import React from 'react';
diff --git a/articles/quickstart/spa/react/download.md b/articles/quickstart/spa/react/download.md
index 132cb4f86d..cec2290b43 100644
--- a/articles/quickstart/spa/react/download.md
+++ b/articles/quickstart/spa/react/download.md
@@ -2,15 +2,15 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to
+1) Set the **Allowed Callback URLs** in the Application Settings to
```text
http://localhost:3000
```
-2) Set **Allowed Web Origins** in the Application Settings to
+2) Set **Allowed Web Origins** in the Application Settings to
```text
http://localhost:3000
```
-3) Set **Allowed Logout URLs** in the Application Settings to
+3) Set **Allowed Logout URLs** in the Application Settings to
```text
http://localhost:3000
```
diff --git a/articles/quickstart/spa/vanillajs/_includes/_centralized_login.md b/articles/quickstart/spa/vanillajs/_includes/_centralized_login.md
index 9f6461a92e..8d85dd25fe 100644
--- a/articles/quickstart/spa/vanillajs/_includes/_centralized_login.md
+++ b/articles/quickstart/spa/vanillajs/_includes/_centralized_login.md
@@ -74,7 +74,7 @@ This article is based on the new SPA SDK available Auth0 application settings as configured above.
+Create an `auth_config.json` in the root of the project. The values from `domain` and `clientId` should be populated from your Auth0 application settings as configured above.
```json
{
diff --git a/articles/quickstart/spa/vanillajs/download.md b/articles/quickstart/spa/vanillajs/download.md
index 132cb4f86d..cec2290b43 100644
--- a/articles/quickstart/spa/vanillajs/download.md
+++ b/articles/quickstart/spa/vanillajs/download.md
@@ -2,15 +2,15 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to
+1) Set the **Allowed Callback URLs** in the Application Settings to
```text
http://localhost:3000
```
-2) Set **Allowed Web Origins** in the Application Settings to
+2) Set **Allowed Web Origins** in the Application Settings to
```text
http://localhost:3000
```
-3) Set **Allowed Logout URLs** in the Application Settings to
+3) Set **Allowed Logout URLs** in the Application Settings to
```text
http://localhost:3000
```
diff --git a/articles/quickstart/spa/vuejs/download.md b/articles/quickstart/spa/vuejs/download.md
index 25b1243099..3f5a35beed 100644
--- a/articles/quickstart/spa/vuejs/download.md
+++ b/articles/quickstart/spa/vuejs/download.md
@@ -2,15 +2,15 @@
To run the sample follow these steps:
-1) Set the **Callback URL** in the Application Settings to
+1) Set the **Callback URL** in the Application Settings to
```text
http://localhost:3000
```
-2) Set **Allowed Web Origins** in the Application Settings to
+2) Set **Allowed Web Origins** in the Application Settings to
```text
http://localhost:3000
```
-3) Set **Allowed Logout URLs** in the Application Settings to
+3) Set **Allowed Logout URLs** in the Application Settings to
```text
http://localhost:3000
diff --git a/articles/quickstart/webapp/_includes/_create_and_assign_roles.md b/articles/quickstart/webapp/_includes/_create_and_assign_roles.md
index 4647727818..f3e0826c9d 100644
--- a/articles/quickstart/webapp/_includes/_create_and_assign_roles.md
+++ b/articles/quickstart/webapp/_includes/_create_and_assign_roles.md
@@ -3,7 +3,7 @@
Before you can add Role Based Access Control, you will need to ensure the required roles are created and assigned to the corresponding user(s).
Follow the guidance explained in assign-roles-to-users to ensure your user gets assigned the `admin` role.
-Once the role is created and assigned to the required user(s), you will need to create a rule that adds the role(s) to the Id Token so that it is available to your backend. To do so, go to the new rule page and create an empty rule. Then, use the following code for your rule:
+Once the role is created and assigned to the required user(s), you will need to create a rule that adds the role(s) to the Id Token so that it is available to your backend. To do so, go to the new rule page and create an empty rule. Then, use the following code for your rule:
<% if (typeof(rolesClaimType) !== "undefined") { %>
``` js
diff --git a/articles/quickstart/webapp/_includes/_mfa-enable.md b/articles/quickstart/webapp/_includes/_mfa-enable.md
index 788ab8eac6..4814dee4fc 100644
--- a/articles/quickstart/webapp/_includes/_mfa-enable.md
+++ b/articles/quickstart/webapp/_includes/_mfa-enable.md
@@ -1,4 +1,4 @@
-To enable the Auth0 MFA feature, open the Multi-factor Auth With Guardian page and enable the __Push Notifications__ option as shown below:
+To enable the Auth0 MFA feature, open the Multi-factor Auth With Guardian page and enable the __Push Notifications__ option as shown below:

diff --git a/articles/quickstart/webapp/_includes/_mfa-login.md b/articles/quickstart/webapp/_includes/_mfa-login.md
index 43ae66238b..0e91d41282 100644
--- a/articles/quickstart/webapp/_includes/_mfa-login.md
+++ b/articles/quickstart/webapp/_includes/_mfa-login.md
@@ -1,4 +1,4 @@
-There is no need to update the code you created in the Login step of this tutorial. As soon as a user initiates sign-in they will be prompted to install a second-factor authenticator application (Auth0 Guardian is the default).
+There is no need to update the code you created in the Login step of this tutorial. As soon as a user initiates sign-in they will be prompted to install a second-factor authenticator application (Auth0 Guardian is the default).

diff --git a/articles/quickstart/webapp/aspnet-core-blazor-server/01-login.md b/articles/quickstart/webapp/aspnet-core-blazor-server/01-login.md
index 4420a6c13b..d89302827e 100644
--- a/articles/quickstart/webapp/aspnet-core-blazor-server/01-login.md
+++ b/articles/quickstart/webapp/aspnet-core-blazor-server/01-login.md
@@ -24,7 +24,7 @@ useCase: quickstart
The Callback URL of your application is the URL where Auth0 will redirect to after the user has authenticated in order for the SDK to complete the authentication process.
-You will need to add this URL to the list of Allowed URLs for your application in your Application Settings, this URL will mostly take the format `https://YOUR_APPLICATION_URL/callback`.
+You will need to add this URL to the list of Allowed URLs for your application in your Application Settings, this URL will mostly take the format `https://YOUR_APPLICATION_URL/callback`.
<%= include('../../../_includes/_logout_url', { returnTo: 'http://localhost:3000' }) %>
diff --git a/articles/quickstart/webapp/aspnet-core-blazor-server/download.md b/articles/quickstart/webapp/aspnet-core-blazor-server/download.md
index 8788389076..716f07b7a3 100644
--- a/articles/quickstart/webapp/aspnet-core-blazor-server/download.md
+++ b/articles/quickstart/webapp/aspnet-core-blazor-server/download.md
@@ -2,13 +2,13 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback,https://localhost:7113/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000,https://localhost:7113
diff --git a/articles/quickstart/webapp/aspnet-core/01-login.md b/articles/quickstart/webapp/aspnet-core/01-login.md
index 1697f22b00..deaadad0c4 100644
--- a/articles/quickstart/webapp/aspnet-core/01-login.md
+++ b/articles/quickstart/webapp/aspnet-core/01-login.md
@@ -23,7 +23,7 @@ useCase: quickstart
The Callback URL of your application is the URL where Auth0 will redirect to after the user has authenticated in order for the SDK to complete the authentication process.
-You will need to add this URL to the list of Allowed URLs for your application in your Application Settings, this URL will mostly take the format `https://YOUR_APPLICATION_URL/callback`.
+You will need to add this URL to the list of Allowed URLs for your application in your Application Settings, this URL will mostly take the format `https://YOUR_APPLICATION_URL/callback`.
<%= include('../../../_includes/_logout_url', { returnTo: 'http://localhost:3000' }) %>
diff --git a/articles/quickstart/webapp/aspnet-core/download.md b/articles/quickstart/webapp/aspnet-core/download.md
index 6fcc4a7ce1..5b15cbb798 100644
--- a/articles/quickstart/webapp/aspnet-core/download.md
+++ b/articles/quickstart/webapp/aspnet-core/download.md
@@ -2,13 +2,13 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
diff --git a/articles/quickstart/webapp/aspnet-owin/01-login.md b/articles/quickstart/webapp/aspnet-owin/01-login.md
index b8105c1303..15e4c11ef5 100644
--- a/articles/quickstart/webapp/aspnet-owin/01-login.md
+++ b/articles/quickstart/webapp/aspnet-owin/01-login.md
@@ -21,7 +21,7 @@ sample_download_required_data:
## Install and configure the OpenID Connect middleware
::: note
- This quickstart uses OWIN middleware and as such, you need to use OWIN in your application. If your application is not currently using OWIN, please refer to Microsoft's OWIN documentation to enable it in your application.
+ This quickstart uses OWIN middleware and as such, you need to use OWIN in your application. If your application is not currently using OWIN, please refer to Microsoft's OWIN documentation to enable it in your application.
:::
The easiest way to enable authentication with Auth0 in your ASP.NET MVC application is to use the OWIN OpenID Connect middleware, so install the `Microsoft.Owin.Security.OpenIdConnect` NuGet package first:
diff --git a/articles/quickstart/webapp/aspnet-owin/download.md b/articles/quickstart/webapp/aspnet-owin/download.md
index a5d8b6e621..2a8ddc0c97 100644
--- a/articles/quickstart/webapp/aspnet-owin/download.md
+++ b/articles/quickstart/webapp/aspnet-owin/download.md
@@ -1,11 +1,11 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
```
diff --git a/articles/quickstart/webapp/django/download.md b/articles/quickstart/webapp/django/download.md
index 23b8ad5d47..a098e882df 100644
--- a/articles/quickstart/webapp/django/download.md
+++ b/articles/quickstart/webapp/django/download.md
@@ -1,12 +1,12 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
diff --git a/articles/quickstart/webapp/express/01-login.md b/articles/quickstart/webapp/express/01-login.md
index fea3feac23..eeadd156ab 100644
--- a/articles/quickstart/webapp/express/01-login.md
+++ b/articles/quickstart/webapp/express/01-login.md
@@ -18,7 +18,7 @@ github:
## Configure Auth0
-You will need to register your application with Auth0 in order to start authenticating users. Go to the Applications screen in the Auth0 dashboard, create a new **Regular Web Application**, and follow the steps below.
+You will need to register your application with Auth0 in order to start authenticating users. Go to the Applications screen in the Auth0 dashboard, create a new **Regular Web Application**, and follow the steps below.
### 1. Configure Callback URL
@@ -54,8 +54,8 @@ The Express OpenID Connect library provides the `auth` router in order to attach
- `auth0Logout` - Uses Auth0 logout feature
- `baseURL` - The URL where the application is served
- `secret` - A long, random string used to encrypt the session cookie
-- `issuerBaseURL` - The Domain as a secure URL found in your Application settings
-- `clientID` - The Client ID found in your Application settings
+- `issuerBaseURL` - The Domain as a secure URL found in your Application settings
+- `clientID` - The Client ID found in your Application settings
Here is an example configuration using this router:
diff --git a/articles/quickstart/webapp/express/download.md b/articles/quickstart/webapp/express/download.md
index 806bcec21a..e9d2d24e91 100644
--- a/articles/quickstart/webapp/express/download.md
+++ b/articles/quickstart/webapp/express/download.md
@@ -2,13 +2,13 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
diff --git a/articles/quickstart/webapp/express/interactive.md b/articles/quickstart/webapp/express/interactive.md
index 9256a7b20e..f1bd5e6423 100644
--- a/articles/quickstart/webapp/express/interactive.md
+++ b/articles/quickstart/webapp/express/interactive.md
@@ -60,8 +60,8 @@ The Express OpenID Connect library provides the `auth` router in order to attach
- `auth0Logout` - Uses Auth0 logout feature
- `baseURL` - The URL where the application is served
- `secret` - A long, random string
-- `issuerBaseURL` - The Domain as a secure URL found in your Application settings
-- `clientID` - The Client ID found in your Application settings
+- `issuerBaseURL` - The Domain as a secure URL found in your Application settings
+- `clientID` - The Client ID found in your Application settings
For additional configuration options visit the API documentation.
diff --git a/articles/quickstart/webapp/golang/download.md b/articles/quickstart/webapp/golang/download.md
index ef75221d43..b2a7add4d8 100644
--- a/articles/quickstart/webapp/golang/download.md
+++ b/articles/quickstart/webapp/golang/download.md
@@ -1,12 +1,12 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
diff --git a/articles/quickstart/webapp/java-ee/download.md b/articles/quickstart/webapp/java-ee/download.md
index 79545983e2..cb0e843940 100644
--- a/articles/quickstart/webapp/java-ee/download.md
+++ b/articles/quickstart/webapp/java-ee/download.md
@@ -1,11 +1,11 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000/
```
diff --git a/articles/quickstart/webapp/java-spring-boot/download.md b/articles/quickstart/webapp/java-spring-boot/download.md
index c64bd29daf..41d63b0ede 100644
--- a/articles/quickstart/webapp/java-spring-boot/download.md
+++ b/articles/quickstart/webapp/java-spring-boot/download.md
@@ -2,12 +2,12 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/login/oauth2/code/auth0
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000/
```
diff --git a/articles/quickstart/webapp/java/_includes/_login.md b/articles/quickstart/webapp/java/_includes/_login.md
index 34b36d985b..754b9e4d74 100644
--- a/articles/quickstart/webapp/java/_includes/_login.md
+++ b/articles/quickstart/webapp/java/_includes/_login.md
@@ -188,7 +188,7 @@ To run the sample from a terminal, change the directory to the root folder of th
./gradlew clean appRun
```
-After a few seconds, the application will be accessible on `http://localhost:3000/`. Try to access the protected resource http://localhost:3000/portal/home and note how you're redirected by the `Auth0Filter` to the Auth0 Login Page. The widget displays all the social and database connections that you have defined for this application in the dashboard.
+After a few seconds, the application will be accessible on `http://localhost:3000/`. Try to access the protected resource http://localhost:3000/portal/home and note how you're redirected by the `Auth0Filter` to the Auth0 Login Page. The widget displays all the social and database connections that you have defined for this application in the dashboard.

diff --git a/articles/quickstart/webapp/java/_includes/_setup.md b/articles/quickstart/webapp/java/_includes/_setup.md
index 7bbada705e..753e49ee3a 100644
--- a/articles/quickstart/webapp/java/_includes/_setup.md
+++ b/articles/quickstart/webapp/java/_includes/_setup.md
@@ -56,7 +56,7 @@ Your Java App needs some information in order to authenticate against your Auth0
```
-This information will be used to configure the **auth0-java-mvc-commons** library to enable users to login to your application. To learn more about the library, including its various configuration options, see the librarys documentation.
+This information will be used to configure the **auth0-java-mvc-commons** library to enable users to login to your application. To learn more about the library, including its various configuration options, see the library's documentation.
::: panel Check populated attributes
diff --git a/articles/quickstart/webapp/java/download.md b/articles/quickstart/webapp/java/download.md
index 8f4610398e..73515fc8af 100644
--- a/articles/quickstart/webapp/java/download.md
+++ b/articles/quickstart/webapp/java/download.md
@@ -1,11 +1,11 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000/login
```
diff --git a/articles/quickstart/webapp/java/interactive.md b/articles/quickstart/webapp/java/interactive.md
index 9b66f36b7a..093af39845 100644
--- a/articles/quickstart/webapp/java/interactive.md
+++ b/articles/quickstart/webapp/java/interactive.md
@@ -66,7 +66,7 @@ If you are using Maven, add them to your `pom.xml`:
Your Java App needs some information in order to authenticate against your Auth0 account. The samples read this information from the deployment descriptor file `src/main/webapp/WEB-INF/web.xml`, but you could store them anywhere else.
-This information will be used to configure the **auth0-java-mvc-commons** library to enable users to login to your application. To learn more about the library, including its various configuration options, see the librarys documentation.
+This information will be used to configure the **auth0-java-mvc-commons** library to enable users to login to your application. To learn more about the library, including its various configuration options, see the library's documentation.
::: panel Check populated attributes
@@ -149,7 +149,7 @@ To run the sample from a terminal, change the directory to the root folder of th
./gradlew clean appRun
```
-After a few seconds, the application will be accessible on `http://localhost:3000/`. Try to access the protected resource http://localhost:3000/portal/home and note how you're redirected by the `Auth0Filter` to the Auth0 Login Page. The widget displays all the social and database connections that you have defined for this application in the dashboard.
+After a few seconds, the application will be accessible on `http://localhost:3000/`. Try to access the protected resource http://localhost:3000/portal/home and note how you're redirected by the `Auth0Filter` to the Auth0 Login Page. The widget displays all the social and database connections that you have defined for this application in the dashboard.

diff --git a/articles/quickstart/webapp/laravel/01-login.md b/articles/quickstart/webapp/laravel/01-login.md
index dd5c72ef0e..13bcb2ef85 100644
--- a/articles/quickstart/webapp/laravel/01-login.md
+++ b/articles/quickstart/webapp/laravel/01-login.md
@@ -148,7 +148,7 @@ Route::get('/', function () {
## User Management{{{ data-action=code data-code="routes/web.php#26:43" }}}
-You can update user information using the Auth0 Management API. All Management endpoints are accessible through the SDK's `management()` method.
+You can update user information using the Auth0 Management API. All Management endpoints are accessible through the SDK's `management()` method.
**Before making Management API calls you must enable your application to communicate with the Management API.** This can be done from the Auth0 Dashboards API page, choosing `Auth0 Management API`, and selecting the 'Machine to Machine Applications' tab. Authorize your Laravel application, and then click the down arrow to choose the scopes you wish to grant.
diff --git a/articles/quickstart/webapp/nextjs/01-login.md b/articles/quickstart/webapp/nextjs/01-login.md
index b2801221d1..2bc8aef546 100644
--- a/articles/quickstart/webapp/nextjs/01-login.md
+++ b/articles/quickstart/webapp/nextjs/01-login.md
@@ -26,7 +26,7 @@ Run the following command within your project directory to install the Auth0 Nex
npm install @auth0/nextjs-auth0
```
-The SDK exposes methods and variables that help you integrate Auth0 with your Next.js application using Route Handlers on the backend and React Context with React Hooks on the frontend.
+The SDK exposes methods and variables that help you integrate Auth0 with your Next.js application using Route Handlers on the backend and React Context with React Hooks on the frontend.
### Configure the SDK
@@ -50,7 +50,7 @@ The SDK will read these values from the Node.js process environment and automati
### Add the dynamic API route handler
-Create a file at `app/api/auth/auth0/route.js`. This is your Route Handler file with a Dynamic Route Segment.
+Create a file at `app/api/auth/[auth0]/route.js`. This is your Route Handler file with a Dynamic Route Segment.
Then, import the `handleAuth` method from the SDK and call it from the `GET` export.
diff --git a/articles/quickstart/webapp/nextjs/download.md b/articles/quickstart/webapp/nextjs/download.md
index fd839112d6..e1adb730a4 100644
--- a/articles/quickstart/webapp/nextjs/download.md
+++ b/articles/quickstart/webapp/nextjs/download.md
@@ -2,12 +2,12 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to
+1) Set the **Allowed Callback URLs** in the Application Settings to
```text
http://localhost:3000/api/auth/callback
```
-2) Set **Allowed Logout URLs** in the Application Settings to
+2) Set **Allowed Logout URLs** in the Application Settings to
```text
http://localhost:3000
```
diff --git a/articles/quickstart/webapp/nextjs/interactive.md b/articles/quickstart/webapp/nextjs/interactive.md
index fd5e29e63b..66f90bdd8f 100644
--- a/articles/quickstart/webapp/nextjs/interactive.md
+++ b/articles/quickstart/webapp/nextjs/interactive.md
@@ -38,7 +38,7 @@ Run the following command within your project directory to install the Auth0 Nex
npm i @auth0/nextjs-auth0
```
-The SDK exposes methods and variables that help you integrate Auth0 with your Next.js application using Route Handlers on the backend and React Context with React Hooks on the frontend.
+The SDK exposes methods and variables that help you integrate Auth0 with your Next.js application using Route Handlers on the backend and React Context with React Hooks on the frontend.
## Configure the SDK {{{ data-action=code data-code=".env.local" }}}
diff --git a/articles/quickstart/webapp/nginx-plus/01-login.md b/articles/quickstart/webapp/nginx-plus/01-login.md
index 548827757c..7d8be88335 100644
--- a/articles/quickstart/webapp/nginx-plus/01-login.md
+++ b/articles/quickstart/webapp/nginx-plus/01-login.md
@@ -19,11 +19,11 @@ This tutorial and seed project have been tested with the following:
* NGINX Plus R24
:::
-**Please follow the steps below to configure your application using NGINX Plus to work with Auth0 and Open ID Connect.**
+**Please follow the steps below to configure your application using **NGINX Plus** to work with Auth0 and Open ID Connect.**
## Install and Enable `nginx-plus-module-njs` Module
-First, you need to install the nginx-plus-module-njs module for NGINX Plus. Follow the dynamic module installation guide to install packages in your host OS.
+First, you need to install the nginx-plus-module-njs module for NGINX Plus. Follow the dynamic module installation guide to install packages in your host OS.
For Linux distributions that use `yum` package manager install as follows:
```bash
diff --git a/articles/quickstart/webapp/php/01-login.md b/articles/quickstart/webapp/php/01-login.md
index 2971e907da..a9fcff579a 100644
--- a/articles/quickstart/webapp/php/01-login.md
+++ b/articles/quickstart/webapp/php/01-login.md
@@ -27,7 +27,7 @@ Let's create a sample application that authenticates a user with a PHP applicati
The Auth0 PHP SDK supports many PHP-FIG standards offering interoperability options with your architecture. Two of particular importance are PSR-17 and PSR-18. These standards allow you to plug-in networking components of your choice to handle messaging and requests. You will need to install compatible libraries in your project for the SDK to use.
-The most prolific networking library for PHP is Guzzle, although many are available to pick from within the PHP community. Let's use Guzzle for this sample application. Once again, from your project directory, run the following shell command:
+The most prolific networking library for PHP is Guzzle, although many are available to pick from within the PHP community. Let's use Guzzle for this sample application. Once again, from your project directory, run the following shell command:
```sh
composer require guzzlehttp/guzzle guzzlehttp/psr7 http-interop/http-factory-guzzle
diff --git a/articles/quickstart/webapp/php/download.md b/articles/quickstart/webapp/php/download.md
index db116dff68..c4da3162ad 100644
--- a/articles/quickstart/webapp/php/download.md
+++ b/articles/quickstart/webapp/php/download.md
@@ -1,12 +1,12 @@
To run the sample follow these steps:
-1. Set the **Allowed Callback URLs** in the Application Settings to:
+1. Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://127.0.0.1:3000/callback
```
-2. Set the **Allowed Logout URLs** in the Application Settings to:
+2. Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://127.0.0.1:3000/logout
diff --git a/articles/quickstart/webapp/python/download.md b/articles/quickstart/webapp/python/download.md
index db8a7a9f27..31aac47d7a 100644
--- a/articles/quickstart/webapp/python/download.md
+++ b/articles/quickstart/webapp/python/download.md
@@ -1,12 +1,12 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
```
diff --git a/articles/quickstart/webapp/rails/download.md b/articles/quickstart/webapp/rails/download.md
index f786019c4e..2a4cda9a35 100644
--- a/articles/quickstart/webapp/rails/download.md
+++ b/articles/quickstart/webapp/rails/download.md
@@ -1,12 +1,12 @@
To run the sample follow these steps:
-1) Set the **Allowed Callback URLs** in the Application Settings to:
+1) Set the **Allowed Callback URLs** in the Application Settings to:
```text
http://localhost:3000/auth/auth0/callback
```
-2) Set the **Allowed Logout URLs** in the Application Settings to:
+2) Set the **Allowed Logout URLs** in the Application Settings to:
```text
http://localhost:3000
diff --git a/articles/quickstart/webapp/rails/interactive.md b/articles/quickstart/webapp/rails/interactive.md
index 28989c6b13..8106ffb50c 100644
--- a/articles/quickstart/webapp/rails/interactive.md
+++ b/articles/quickstart/webapp/rails/interactive.md
@@ -131,7 +131,7 @@ Still having issues? Check out our Concern to control access to routes that can be shared across multiple controllers. The concern should automatically redirect to Auth0 when the user is unauthenticated. Otherwise, the concern should return the current user profile.
+To display the user's profile, your application should provide a protected route. You can use a Concern to control access to routes that can be shared across multiple controllers. The concern should automatically redirect to Auth0 when the user is unauthenticated. Otherwise, the concern should return the current user profile.
Once you have a Concern, include it in any controller that requires a logged in user. You can then access the user from the session `session[:userinfo]` as in the following example:
diff --git a/snippets/native-platforms/android-facebook-login/facebook-token-exchange.md b/snippets/native-platforms/android-facebook-login/facebook-token-exchange.md
index 3e68963705..2253165145 100644
--- a/snippets/native-platforms/android-facebook-login/facebook-token-exchange.md
+++ b/snippets/native-platforms/android-facebook-login/facebook-token-exchange.md
@@ -51,7 +51,7 @@ private void exchangeTokens(@NonNull String sessionToken, @NonNull String userPr
::: note
It's a good practice to keep all the values that you know won't change as constants at the top of the class. The sample makes use of constants for the subject token type, the Facebook permissions, and the Auth0 scopes.
-You can read more about Auth0 scopes in the dedicated [article](/scopes/current/oidc-scopes).
+You can read more about Auth0 scopes in the dedicated article.
:::
diff --git a/snippets/server-platforms/php/install.md b/snippets/server-platforms/php/install.md
index ca03bbb7ba..b0ea28b88d 100644
--- a/snippets/server-platforms/php/install.md
+++ b/snippets/server-platforms/php/install.md
@@ -1,4 +1,4 @@
-The Auth0 PHP SDK requires [Composer](https://getcomposer.org/doc/00-intro.md#installation-linux-unix-macos), a tool for dependency management in PHP. Composer allows you to declare the dependent libraries your project needs and installs them for you. Please ensure Composer is installed and accessible from your shell before continuing.
+The Auth0 PHP SDK requires Composer, a tool for dependency management in PHP. Composer allows you to declare the dependent libraries your project needs and installs them for you. Please ensure Composer is installed and accessible from your shell before continuing.
Run the following shell command within your project directory to install the Auth0 PHP SDK: