Merge pull request #290650 from Akhilesh-microsoft/ACA/authentication_twitter

[ACA: authentication-twitter]: Verified the article, reviewed the content, and fixed all editorial issues. Updated ms.date w.r.t freshness pass.

Author: prmerger-automator[bot]

articles/container-apps/authentication-twitter.md

@@ -5,7 +5,7 @@ services: container-apps
 author: craigshoemaker
 ms.service: azure-container-apps
 ms.topic: how-to
-ms.date: 04/20/2022
+ms.date: 11/18/2024
 ms.author: cshoe
 ---
 
@@ -17,7 +17,7 @@ To complete the procedure in this article, you need an X account that has a veri
 
 ## <a name="twitter-register"> </a>Register your application with X
 
-1. Sign in to the [Azure portal] and go to your application. Copy your **URL**. You'll use it to configure your X app.
+1. Sign in to the [Azure portal] and go to your application. Copy your **URL**, later you use it to configure your X app.
 1. Go to the [X Developers] website, sign in with your X account credentials, and select **Create an app**.
 1. Enter the **App name** and the **Application description** for your new app. Paste your application's **URL** into the **Website URL** field. In the **Callback URLs** section, enter the HTTPS URL of your container app and append the path `/.auth/login/x/callback`. For example, `https://<hostname>.azurecontainerapps.io/.auth/login/x/callback`.
 1. At the bottom of the page, type at least 100 characters in **Tell us how this app will be used**, then select **Create**. Select **Create** again in the pop-up. The application details are displayed.
@@ -36,15 +36,15 @@ To complete the procedure in this article, you need an X account that has a veri
 1. Select **Authentication** in the menu on the left. Select **Add identity provider**.
 1. Select **Twitter** in the identity provider dropdown. Paste in the `API key` and `API secret key` values that you obtained previously.
 
-    The secret will be stored as [secret](manage-secrets.md) in your container app.
+    The secret is stored as [secret](manage-secrets.md) in your container app.
 
-1. If you're configuring the first identity provider for this application, you'll also be prompted with a **Container Apps authentication settings** section. Otherwise, you may move on to the next step.
+1. If you're configuring the first identity provider for this application, you're prompted with a **Container Apps authentication settings** section. Otherwise, you move on to the next step.
 
     These options determine how your application responds to unauthenticated requests. The default selections redirect all requests to sign in with this new provider. You can change customize this behavior now or adjust these settings later from the main **Authentication** screen by choosing **Edit** next to **Authentication settings**. To learn more about these options, see [Authentication flow](authentication.md#authentication-flow).
 
 1. Select **Add**.
 
-You're now ready to use X for authentication in your app. The provider will be listed on the **Authentication** screen. From there, you can edit or delete this provider configuration.
+You're now ready to use X for authentication in your app. The provider is listed on the **Authentication** screen. From there, you can edit or delete this provider configuration.
 
 ## Working with authenticated users