Standardize titles/references to flows and use of "single-page" terminology (#7524)

* Standardize references to flows and use of single-page term

* Update application section index with new filenames

* Update auth sequence media

* fix missing link

Author: rkhoriander

CONTRIBUTING.md

@@ -167,7 +167,7 @@ Description
 :::
 
 ::: panel-warning Security Warning
-It is important to understand that the Authorization Code flow should only be used in cases such as a Regular Web Application where the Client Secret can be safely stored. In cases such as a Single Page Application, the Client Secret is available to the client (in the web browser), so the integrity of the Client Secret cannot be maintained. That is why the [Single-Page Login Flow](/flows/concepts/single-page-login-flow) is more appropriate in that case.
+It is important to understand that the Authorization Code flow should only be used in cases such as a Regular Web Application where the Client Secret can be safely stored. In cases such as a Single-Page Application, the Client Secret is available to the client (in the web browser), so the integrity of the Client Secret cannot be maintained. That is why the [Implicit Flow](/flows/concepts/implicit) is more appropriate in that case.
 :::
 ```
 

articles/api-auth/config/using-the-auth0-dashboard.md

@@ -10,7 +10,7 @@ useCase: secure-api
 
 # Set up a Client Credentials Grant using the Dashboard
 
-Auth0 lets you authorize applications that have the **Client Credentials** grant type enabled to call APIs using the [Machine-to-Machine (M2M) Flow](/flows/concepts/m2m-flow). 
+Auth0 lets you authorize applications that have the **Client Credentials** grant type enabled to call APIs using the [Client Credentials Flow](/flows/concepts/client-credentials). 
 
 By default, the **Client Credentials** grant is enabled for all Machine-to-Machine Applications and Regular Web Applications, but they are _not yet_ authorized to call any API.
 
@@ -29,7 +29,7 @@ To authorize the applications to call an API:
 ## Keep reading
 
 :::next-steps
-* [Call API using the Machine-to-Machine (M2M) Flow](/flows/guides/m2m-flow/call-api-using-m2m-flow)
+* [Call API using the Client Credentials Flow](/flows/guides/client-credentials/call-api-client-credentials)
 * [How to change the scopes and add custom claims to a token using Hooks](/api-auth/tutorials/client-credentials/customize-with-hooks)
 * [How to add custom claims to a token using Rules](/scopes/current/sample-use-cases#add-custom-claims-to-a-token)
 :::

articles/api-auth/config/using-the-management-api.md

@@ -11,7 +11,7 @@ useCase: secure-api
 
 # Set up a Client Credentials Grant using the Management API
 
-Auth0 lets you authorize applications that have the 'Client Credentials' grant type enabled to call APIs using the [Machine-to-Machine (M2M) Flow](/flows/concepts/m2m-flow). 
+Auth0 lets you authorize applications that have the 'Client Credentials' grant type enabled to call APIs using the [Client Credentials Flow](/flows/concepts/client-credentials). 
 
 By default, all Machine-to-Machine Applications and Regular Web Applications have the 'Client Credentials' grant enabled, but they are not authorized to call any API.
 
@@ -59,12 +59,12 @@ Sample response:
 }
 ```
 
-That's it, you are done! Now that all the elements are in place, you can request Access Tokens for your API from Auth0 using the Machine-to-Machine (M2M) Flow.
+That's it, you are done! Now that all the elements are in place, you can request Access Tokens for your API from Auth0 using the Client Credentials Flow.
 
 ## Keep reading
 
 :::next-steps
-* [Call API using the Machine-to-Machine (M2M) Flow](/flows/guides/m2m-flow/call-api-using-m2m-flow)
+* [Call API using the Client Credentials Flow](/flows/guides/client-credentials/call-api-client-credentials)
 * [How to change the scopes and add custom claims to a token using Hooks](/api-auth/tutorials/client-credentials/customize-with-hooks)
 * [How to add custom claims to a token using Rules](/scopes/current/sample-use-cases#add-custom-claims-to-a-token)
 :::

articles/api-auth/dynamic-client-registration.md

@@ -111,7 +111,7 @@ Also, keep in mind that third-party developers are not allowed to modify the app
 
 Now that you have a Client ID and Secret, you can configure your application to authenticate users with Auth0.
 
-We will go through a simple example, that shows how to call an API from a client-side web app, using the [Single-Page Login Flow](/flows/guides/single-page-login-flow/call-api-using-single-page-login-flow). For a list of tutorials on how to authenticate and authorize users, based on your application type, see the [API Authorization](/api-auth) page.
+We will go through a simple example, that shows how to call an API from a client-side web app, using the [Implicit Flow](/flows/guides/implicit/call-api-implicit). For a list of tutorials on how to authenticate and authorize users, based on your application type, see the [API Authorization](/api-auth) page.
 
 First, you need to configure your application to send the user to the authorization URL:
 

articles/api-auth/grant/hybrid.md

@@ -13,16 +13,16 @@ useCase:
 
 The Hybrid Flow is an OpenID Connect (OIDC) flow that draws from the following:
 
-1. [Regular Web App Login Flow](/flows/concepts/regular-web-app-login-flow)
-2. [Single-Page Login Flow](/flows/concepts/single-page-login-flow)
+1. [Authorization Code Flow](/flows/concepts/auth-code)
+2. [Implicit Flow](/flows/concepts/implicit)
 
 The Hybrid Flow enables use cases where your application can immediately use an ID token to access information about the user while obtaining an authorization code that can be exchanged for an Access Token (therefore gaining access to protected resources for an extended period of time).
 
 ## Background
 
-With the [Regular Web App Login Flow](/flows/concepts/regular-web-app-login-flow), Auth0 sends you an authorization code, which your app then sends in to retrieve tokens. Your application authenticates itself with a Client ID and Client Secret stored securely on your server.
+With the [Authorization Code Flow](/flows/concepts/auth-code), Auth0 sends you an authorization code, which your app then sends in to retrieve tokens. Your application authenticates itself with a Client ID and Client Secret stored securely on your server.
 
-On the other hand, the [Single-Page Login Flow](/flows/concepts/single-page-login-flow) allows you to request Access Tokens without needing to authenticate your application. Auth0 verifies your app's identity based on the provided redirect URI. Because of this, you shouldn't utilize long-lived Access Tokens, and you cannot use Refresh Tokens.
+On the other hand, the [Implicit Flow](/flows/concepts/implicit) allows you to request Access Tokens without needing to authenticate your application. Auth0 verifies your app's identity based on the provided redirect URI. Because of this, you shouldn't utilize long-lived Access Tokens, and you cannot use Refresh Tokens.
 
 ## The Hybrid Flow
 
@@ -60,7 +60,7 @@ For details on how to implement this using Auth0, refer to [Execute the Hybrid F
 - [Execute the Hybrid Flow](/api-auth/tutorials/hybrid-flow)
 - [How to configure an API in Auth0](/apis)
 - [Why you should always use Access Tokens to secure an API](/api-auth/why-use-access-tokens-to-secure-apis)
-- [Application authentication for regular web apps](/flows/concepts/regular-web-app-login-flow)
-- [Application authentication for single-page apps](/flows/concepts/single-page-login-flow)
+- [Application authentication for regular web apps](/flows/concepts/auth-code)
+- [Application authentication for single-page apps](/flows/concepts/implicit)
 - [Tokens used by Auth0](/tokens)
 :::

articles/api-auth/grant/implicit.md

@@ -14,7 +14,7 @@ useCase:
 
 <%= include('../../_includes/_pipeline2') %>
 
-In order to access an API from a [client-side app](/quickstart/spa) (typically a Single Page Application or a Mobile Application), you need to implement the OAuth 2.0 **Implicit Grant**. In this document we will see how this flow works.
+In order to access an API from a [client-side app](/quickstart/spa) (typically a Single-Page Application or a Mobile Application), you need to implement the OAuth 2.0 **Implicit Grant**. In this document we will see how this flow works.
 
 ::: note
 If you need a refresher on the OAuth 2.0 protocol, you can go through our [OAuth 2.0](/protocols/oauth2) article.
@@ -32,7 +32,7 @@ Once the user authenticates, the application receives the Access Token in the ha
 
  1. Auth0 authenticates the user. The first time the user goes through this flow a consent page will be shown where the permissions, that will be given to the Application, are listed (for example: post messages, list contacts, and so forth).
 
- 1. Auth0 redirects the user to the app with an [Access Token](/tokens/overview-access-tokens) (and optionally an [ID Token](/tokens/id-token)) in the hash fragment of the URI. The app can now extract the tokens from the hash fragment. In a Single Page Application (SPA) this would be done using Javascript and in a Mobile Application this is typically handled by interacting with a Web View.
+ 1. Auth0 redirects the user to the app with an [Access Token](/tokens/overview-access-tokens) (and optionally an [ID Token](/tokens/id-token)) in the hash fragment of the URI. The app can now extract the tokens from the hash fragment. In a Single-Page Application (SPA) this would be done using Javascript and in a Mobile Application this is typically handled by interacting with a Web View.
 
  1. The app can use the Access Token to call the API on behalf of the user.
 

articles/api-auth/grant/password.md

@@ -17,8 +17,8 @@ useCase:
 Highly trusted applications can use this flow to access APIs. In this flow the end-user is asked to fill in credentials (username/password), typically using an interactive form. This information is sent to the backend and from there to Auth0.
 
 You should use this flow **only if** the following apply:
-- The application is absolutely trusted with the user's credentials. For [Single-Page Applications](/flows/concepts/single-page-login-flow) and [Native/Mobile Apps](/flows/concepts/mobile-login-flow) we recommend using web flows instead.
-- Using a redirect-based flow is not possible. If this is not the case and redirects are possible in your application, you should use the [Regular Web App Login Flow](/flows/concepts/regular-web-app-login-flow) instead.
+- The application is absolutely trusted with the user's credentials. For [Single-Page Applications](/flows/concepts/implicit) and [Native/Mobile Apps](/flows/concepts/auth-code-pkce) we recommend using web flows instead.
+- Using a redirect-based flow is not possible. If this is not the case and redirects are possible in your application, you should use the [Authorization Code Flow](/flows/concepts/auth-code) instead.
 
 ::: note
 If you need a refresher on the OAuth 2.0 protocol, you can go through our [OAuth 2.0](/protocols/oauth2) article.

articles/api-auth/index.md

@@ -38,44 +38,44 @@ In this page you can find a list of resources that can help you secure your APIs
     </p>
   </li>
   <li>
-      <i class="icon icon-budicon-715"></i><a href="/flows/guides/regular-web-app-login-flow/call-api-using-regular-web-app-login-flow">Call Your API from a Regular Web App</a>
+      <i class="icon icon-budicon-715"></i><a href="/flows/guides/auth-code/call-api-auth-code">Call Your API from a Regular Web App</a>
     <p>
       If your application executes on a server and you want to configure it to use OAuth 2.0 to access an API, read these docs.
     </p>
     <ul>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/regular-web-app-login-flow">Overview of the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/auth-code">Overview of the flow</a>
       </li>
       <li>
-        <i class="icon icon-budicon-695"></i><a href/flows/guides/regular-web-app-login-flow/call-api-using-regular-web-app-login-flow">Executing the flow</a>
+        <i class="icon icon-budicon-695"></i><a href/flows/guides/auth-code/call-api-auth-code">Executing the flow</a>
       </li>
     </ul>
   </li>
   <li>
-    <i class="icon icon-budicon-715"></i><a href="/flows/guides/mobile-login-flow/call-api-using-mobile-login-flow">Call Your API from a Native/Mobile App</a>
+    <i class="icon icon-budicon-715"></i><a href="/flows/guides/auth-code-pkce/call-api-auth-code-pkce">Call Your API from a Native/Mobile App</a>
     <p>
       If your application is a native app and you want to configure it to use OAuth 2.0 to access an API, read these docs.
     </p>
     <ul>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/mobile-login-flow">Overview of the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/auth-code-pkce">Overview of the flow</a>
       </li>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/guides/mobile-login-flow/call-api-using-mobile-login-flow">Executing the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/guides/auth-code-pkce/call-api-auth-code-pkce">Executing the flow</a>
       </li>
     </ul>
   </li>
   <li>
-    <i class="icon icon-budicon-715"></i><a href="/flows/guides/single-page-login-flow/call-api-using-single-page-login-flow">Call Your API from a Single-Page App</a>
+    <i class="icon icon-budicon-715"></i><a href="/flows/guides/implicit/call-api-implicit">Call Your API from a Single-Page App</a>
     <p>
       If your application is a JavaScript-centric app executing on the browser, and you want to configure it to use OAuth 2.0 to access an API, read these docs.
     </p>
     <ul>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/single-page-login-flow">Overview of the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/implicit">Overview of the flow</a>
       </li>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/guides/single-page-login-flow/call-api-using-single-page-login-flow">Executing the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/guides/implicit/call-api-implicit">Executing the flow</a>
       </li>
       <li>
         <i class="icon icon-budicon-695"></i><a href="/api-auth/tutorials/silent-authentication">Silent authentication for SPAs</a>
@@ -89,16 +89,16 @@ In this page you can find a list of resources that can help you secure your APIs
     </ul>
   </li>
   <li>
-    <i class="icon icon-budicon-715"></i><a href="/flows/guides/m2m-flow/call-api-using-m2m-flow">Call Your API from a Machine-to-Machine App</a>
+    <i class="icon icon-budicon-715"></i><a href="/flows/guides/client-credentials/call-api-client-credentials">Call Your API from a Machine-to-Machine App</a>
     <p>
       If you want to implement server-to-server interaction, and you want to configure it to use OAuth 2.0, read these docs.
     </p>
     <ul>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/m2m-flow">Overview of the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/concepts/client-credentials">Overview of the flow</a>
       </li>
       <li>
-        <i class="icon icon-budicon-695"></i><a href="/flows/guides/m2m-flow/call-api-using-m2m-flow">Executing the flow</a>
+        <i class="icon icon-budicon-695"></i><a href="/flows/guides/client-credentials/call-api-client-credentials">Executing the flow</a>
       </li>
       <li>
         <i class="icon icon-budicon-695"></i><a href="/api-auth/config/using-the-auth0-dashboard">How to set up a Client Grant using the Dashboard</a>