Merge pull request #314801 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/active-directory-b2c/add-api-connector.md

@@ -25,7 +25,7 @@ ms.custom:
 
 [!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
 
-As a developer or IT administrator, you can use API connectors to integrate your sign-up user flows with REST APIs to customize the sign-up experience and integrate with external systems. At the end of this walkthrough, you'll be able to create an Azure AD B2C user flow that interacts with [REST API services](api-connectors-overview.md) to modify your sign-up experiences. 
+As a developer or IT administrator, you can use API connectors to integrate sign-up user flows with REST APIs, enabling customization of the sign-up experience and integration with external systems. At the end of this walkthrough, you'll be able to create an Azure AD B2C user flow that interacts with [REST API services](api-connectors-overview.md) to modify your sign-up experiences. 
 
 ::: zone pivot="b2c-user-flow"
 You can create an API endpoint using one of our [samples](api-connector-samples.md#api-connector-rest-api-samples).
@@ -515,7 +515,7 @@ Add the validation technical profile reference to the sign-up technical profile,
             <OutputClaim ClaimTypeReferenceId="reenterPassword" Required="true"/>
             <OutputClaim ClaimTypeReferenceId="displayName"/>
             <OutputClaim ClaimTypeReferenceId="givenName"/>
-            <OutputClaim ClaimTypeReferenceId="surName"/>
+            <OutputClaim ClaimTypeReferenceId="surname"/>
             <!-- Required to present the text box to collect the data from the user -->
             <OutputClaim ClaimTypeReferenceId="loyaltyId"/>
             <!-- Required to pass the promoCode returned from "REST-ValidateProfile" 

articles/azure-resource-manager/bicep/bicep-functions-resource.md

@@ -681,7 +681,7 @@ The identifier is returned in the following format:
 
 You use this function to get the resource ID for resources that are [deployed to the subscription](deploy-to-subscription.md) rather than a resource group. The returned ID differs from the value returned by the [resourceId](#resourceid) function by not including a resource group value.
 
-### subscriptionResourceID example
+### subscriptionResourceId example
 
 The following Bicep file assigns a built-in role. You can deploy it to either a resource group or subscription. It uses the `subscriptionResourceId` function to get the resource ID for built-in roles.
 

articles/sentinel/connect-logstash-data-connection-rules.md

@@ -74,6 +74,10 @@ The Microsoft Sentinel output plugin for Logstash sends JSON-formatted data to y
     - 7.0 - 7.17.13
     - 8.0 - 8.9
     - 8.11 - 8.15
+    - 8.19.2
+    - 9.0.8
+    - 9.1.10
+    - 9.2.4 - 9.2.5
 
     > [!NOTE]
     > If you use Logstash 8, we recommended that you [disable ECS in the pipeline](https://www.elastic.co/guide/en/logstash/8.4/ecs-ls.html).