Merge pull request #244352 from msmbaldwin/fist-first

Fixing fist -> first typos

Author: prmerger-automator[bot]

articles/active-directory-b2c/custom-policies-series-overview.md

@@ -30,7 +30,7 @@ While you can use pre-made [custom policy starter pack](./tutorial-create-user-f
 
 ## Select an article 
 
-This how-to guide series consists of multiple articles. We recommend that you start this series from the fist article. For each article (except the first one), you're expected to use the custom policy you write in the preceding article.
+This how-to guide series consists of multiple articles. We recommend that you start this series from the first article. For each article (except the first one), you're expected to use the custom policy you write in the preceding article.
 
 |Article  | What you'll learn  |
 |---------|---------|

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in-federation.md

@@ -674,7 +674,7 @@ Use the following steps to add a combined local and social account:
         </UserJourneys>-->
     ```
 
-    In the fist step, we specify the options a user needs to choose from in their journey, local or social authentication. In the steps that follow, we use preconditions to track the option the user picked or the stage of the journey at which the user is. For example, we use the `authenticationSource` claim to differentiate between a local authentication journey and a social authentication journey.  
+    In the first step, we specify the options a user needs to choose from in their journey, local or social authentication. In the steps that follow, we use preconditions to track the option the user picked or the stage of the journey at which the user is. For example, we use the `authenticationSource` claim to differentiate between a local authentication journey and a social authentication journey.  
 
 1. In the `RelyingParty` section, change *DefaultUserJourney's* `ReferenceId` to `LocalAndSocialSignInAndSignUp`  
 

articles/active-directory/develop/includes/web-api/quickstart-dotnet-native-aspnet.md

@@ -136,7 +136,7 @@ Start both projects. For Visual Studio users;
 
 1. For both projects choose **Start** as the action
 
-1. Ensure the TodoListService service starts first by moving it to the fist position in the list, using the up arrow.
+1. Ensure the TodoListService service starts first by moving it to the first position in the list, using the up arrow.
 
 Sign in to run your TodoListClient project.
 

articles/active-directory/develop/quickstart-v2-dotnet-native-aspnet.md

@@ -147,7 +147,7 @@ ms.custom: devx-track-csharp, aaddev, identityplatformtop40, "scenarios:getting-
 > 
 > 1. For both projects choose **Start** as the action
 > 
-> 1. Ensure the TodoListService service starts first by moving it to the fist position in the list, using the up arrow.
+> 1. Ensure the TodoListService service starts first by moving it to the first position in the list, using the up arrow.
 > 
 > Sign in to run your TodoListClient project.
 > 

articles/active-directory/develop/web-api-quickstart-portal-dotnet-native-aspnet.md

@@ -148,7 +148,7 @@ ms.custom: devx-track-csharp, aaddev, identityplatformtop40, "scenarios:getting-
 > 
 > 1. For both projects choose **Start** as the action
 > 
-> 1. Ensure the TodoListService service starts first by moving it to the fist position in the list, using the up arrow.
+> 1. Ensure the TodoListService service starts first by moving it to the first position in the list, using the up arrow.
 > 
 > Sign in to run your TodoListClient project.
 > 

articles/azure-cache-for-redis/cache-moving-resources.md

@@ -75,7 +75,7 @@ After geo-replication is configured, the following restrictions apply to your li
 
 ### Move
 
-1. To link two caches together for geo-replication, fist select **Geo-replication** from the Resource menu of the cache that you intend to be the primary linked cache. Next, select **Add cache replication link** from **Geo-replication** on the left.
+1. To link two caches together for geo-replication, first select **Geo-replication** from the Resource menu of the cache that you intend to be the primary linked cache. Next, select **Add cache replication link** from **Geo-replication** on the left.
 
     :::image type="content" source="media/cache-how-to-geo-replication/cache-geo-location-menu.png" alt-text="Screenshot showing the cache's Geo-replication menu.":::
 

articles/virtual-network/ip-services/manage-custom-ip-address-prefix.md

@@ -150,7 +150,7 @@ The operation is asynchronous. You can check the status by reviewing the **Commi
 To fully remove a custom IP prefix, it must be deprovisioned and then deleted. 
 
 > [!NOTE]
-> If there is a requirement to migrate an provisioned range from one region to the other, the original custom IP prefix must be fully removed from the fist region before a new custom IP prefix with the same address range can be created in another region.
+> If there is a requirement to migrate an provisioned range from one region to the other, the original custom IP prefix must be fully removed from the first region before a new custom IP prefix with the same address range can be created in another region.
 >
 > The estimated time to complete the deprovisioning process is anywhere from 30 to 60 minutes.