Merge pull request #292404 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: Albertyang0

articles/app-service/overview-access-restrictions.md

@@ -89,9 +89,9 @@ Multi-source rules are defined the same way you define single-source rules, but
 
 You can't create these rules in the portal, but you can modify an existing service tag or IP-based rule and add more sources to the rule.
 
-### Http header filtering for site access restriction rules
+### HTTP header filtering for site access restriction rules
 
-For any rule, regardless of type, you can add http header filtering. Http header filters allow you to further inspect the incoming request and filter based on specific http header values. Each header can have up to eight values per rule. The following lists the supported http headers:
+For any rule, regardless of type, you can add http header filtering. HTTP header filters allow you to further inspect the incoming request and filter based on specific http header values. Each header can have up to eight values per rule. The following lists the supported http headers:
 
 * **X-Forwarded-For**. [Standard header](https://developer.mozilla.org/docs/Web/HTTP/Headers/X-Forwarded-For) for identifying the originating IP address of a client connecting through a proxy server. Accepts valid IP addresses.
 * **X-Forwarded-Host**. [Standard header](https://developer.mozilla.org/docs/Web/HTTP/Headers/X-Forwarded-Host) for identifying the original host requested by the client. Accepts any string up to 64 characters in length.

articles/azure-app-configuration/monitor-app-configuration-reference.md

@@ -20,9 +20,9 @@ Resource Provider and Type: [App Configuration Platform Metrics](/azure/azure-mo
 
 | Metric | Unit | Description |
 |-------|-----| ----- |
-| Http Incoming Request Count	| Count	| Total number of incoming Http Request |
-| Http Incoming Request Duration | Milliseconds | Server side duration of an Http Request |
-| Throttled Http Request Count | Count |	Throttled requests are Http requests that receive a response with a status code of 429 |
+| HTTP Incoming Request Count	| Count	| Total number of incoming HTTP Request |
+| HTTP Incoming Request Duration | Milliseconds | Server side duration of an HTTP Request |
+| Throttled HTTP Request Count | Count |	Throttled requests are HTTP requests that receive a response with a status code of 429 |
 | Daily Storage Usage | Percent |	Represents the amount of storage in use as a percentage of the maximum allowance. This metric is updated at least once daily. |
 | Request Quota Usage | Percent |	Represents the current total request usage in percentage. |
 | Replication Latency | Milliseconds |	Represents the average time it takes for a replica to be consistent with current state. |
@@ -36,9 +36,9 @@ App Configuration has the following dimensions associated with its metr
 
 | Metric Name | Dimension description |
 |-------|-----|
-| Http Incoming Request Count | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication.   |
-| Http Incoming Request Duration | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication. |
-| Throttled Http Request Count | The **Endpoint** of each request is included as a dimension.  |
+| HTTP Incoming Request Count | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication.   |
+| HTTP Incoming Request Duration | The supported dimensions are the **HttpStatusCode**, **AuthenticationScheme**, and **Endpoint** of each request. **AuthenticationScheme** can be filtered by "AAD" or "HMAC" authentication. |
+| Throttled HTTP Request Count | The **Endpoint** of each request is included as a dimension.  |
 | Daily Storage Usage | This metric does not have any dimensions.  |
 | Request Quota Usage | The supported dimensions are the **OperationType** ("Read"or "Write") and **Endpoint** of each request.  |
 | Replication Latency | The **Endpoint** of the replica that data was replicated to is included as a dimension.  |
@@ -62,7 +62,7 @@ This section refers to all of the Azure Monitor Logs Kusto tables re
 |Resource type | Notes |
 |-------|-----|
 | [AACAudit](/azure/azure-monitor/reference/tables/AACAudit) | Azure App Configuration audit logs. |
-| [AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest) | Entries of every Http request sent to a selected app configuration resource. |
+| [AACHttpRequest](/azure/azure-monitor/reference/tables/AACHttpRequest) | Entries of every HTTP request sent to a selected app configuration resource. |
 | [AzureActivity](/azure/azure-monitor/reference/tables/AzureActivity) | Entries from the Azure Activity log that provide insight into any subscription-level or management group level events that have occurred in Azure. |
 
 For a reference of all Azure Monitor Logs / Log Analytics tables, see the [Azure Monitor Log Table Reference](/azure/azure-monitor/reference/tables/microsoft-appconfiguration_configurationstores).
@@ -71,7 +71,7 @@ For a reference of all Azure Monitor Logs / Log Analytics tables, se
 
 App Configuration uses the [AACHttpRequest Table](/azure/azure-monitor/reference/tables/aachttprequest) to store resource log information.
 
-**Http Requests**
+**HTTP Requests**
 
 |Property | Type | Description |
 |-------|-----| ----- |
@@ -81,7 +81,7 @@ App Configuration uses the [AACHttpRequest Table](/azure/azure-monitor/refere
 |CorrelationId|	string|	An ID provided by the client to correlate multiple requests.
 |DurationMs|	int	|The duration of the operation in milliseconds.
 |HitCount|	int	|The number of requests that the record is associated with.
-|Method	string|	HTTP| Http request method (get or post)
+|Method	string|	HTTP| HTTP request method (get or post)
 |RequestId|	string|	Unique request ID generated by server.
 |RequestLength|	int	|Length in bytes of the HTTP request.
 |RequestURI|	string|	URI of the request, can include key and label name. 

articles/azure-app-configuration/monitor-app-configuration.md

@@ -97,9 +97,9 @@ When you create a diagnostic setting, you specify which categories of logs to co
 
 You can analyze metrics for App Configuration with metrics from other Azure services using metrics explorer by opening **Metrics** from the **Azure Monitor** menu. See [Analyze metrics with Azure Monitor metrics explorer](/azure/azure-monitor/essentials/analyze-metrics) for details on using this tool. For App Configuration, the following metrics are collected: 
 
-* Http Incoming Request Count 
-* Http Incoming Request Duration 
-* Throttled Http Request Count (Http status code 429 Responses)
+* HTTP Incoming Request Count 
+* HTTP Incoming Request Duration 
+* Throttled HTTP Request Count (HTTP status code 429 Responses)
 * Daily Storage Usage
 * Request Quota Usage
 * Replication Latency
@@ -133,13 +133,13 @@ Following are sample queries that you can use to help you monitor your App Confi
 
 
 
-* List all Http Requests in the last three days 
+* List all HTTP Requests in the last three days 
     ```Kusto
        AACHttpRequest
         | where TimeGenerated > ago(3d)
     ```
 
-* List all throttled requests (returned Http status code 429 for too many requests) in the last three days 
+* List all throttled requests (returned HTTP status code 429 for too many requests) in the last three days 
     ```Kusto
        AACHttpRequest
         | where TimeGenerated > ago(3d)

articles/azure-functions/durable/durable-functions-dotnet-entities.md

@@ -226,7 +226,7 @@ public static async Task<HttpResponseMessage> DeleteCounter(
 
 ### Example: client reads entity state
 
-The following Azure Http Function implements a GET operation using REST conventions. It reads the current state of the counter entity whose key is passed in the URL path.
+The following Azure HTTP Function implements a GET operation using REST conventions. It reads the current state of the counter entity whose key is passed in the URL path.
 ```csharp
 [FunctionName("GetCounter")]
 public static async Task<HttpResponseMessage> GetCounter(
@@ -266,7 +266,7 @@ public static async Task<int> Run(
 ::: zone pivot="isolated"
 ### Example: client signals entity
 
-The following Azure Http Function implements a DELETE operation using REST conventions. It sends a delete signal to the counter entity whose key is passed in the URL path.
+The following Azure HTTP Function implements a DELETE operation using REST conventions. It sends a delete signal to the counter entity whose key is passed in the URL path.
 
 ```csharp
 [Function("DeleteCounter")]
@@ -282,7 +282,7 @@ public static async Task<HttpResponseData> DeleteCounter(
 
 ### Example: client reads entity state
 
-The following Azure Http Function implements a GET operation using REST conventions. It reads the current state of the counter entity whose key is passed in the URL path.
+The following Azure HTTP Function implements a GET operation using REST conventions. It reads the current state of the counter entity whose key is passed in the URL path.
 
 ```csharp
 [Function("GetCounter")]

articles/azure-health-insights/includes/example-1-inference-follow-up-recommendation-json-request.md

@@ -79,7 +79,7 @@ ms.service: azure-health-insights
                       "code": {
                         "coding": [
                           {
-                            "system": "Https://loinc.org",
+                            "system": "https://loinc.org",
                             "code": "LP207608-3",
                             "display": "ULTRASOUND"
                           }

articles/azure-health-insights/includes/example-2-inference-follow-up-recommendation-json-request.md

@@ -79,7 +79,7 @@ ms.service: azure-health-insights
                       "code": {
                         "coding": [
                           {
-                            "system": "Https://loinc.org",
+                            "system": "https://loinc.org",
                             "code": "LP207608-3",
                             "display": "ULTRASOUND"
                           }

articles/azure-health-insights/includes/example-inference-age-mismatch-json-request.md

@@ -80,7 +80,7 @@ ms.service: azure-health-insights
                       "code": {
                         "coding": [
                           {
-                            "system": "Https://loinc.org",
+                            "system": "https://loinc.org",
                             "code": "41806-1",
                             "display": "CT ABDOMEN"
                           }

articles/azure-health-insights/includes/example-inference-critical-result-json-request.md

@@ -79,7 +79,7 @@ ms.service: azure-health-insights
                       "code": {
                         "coding": [
                           {
-                            "system": "Https://loinc.org",
+                            "system": "https://loinc.org",
                             "code": "26086-9",
                             "display": "XR KNEE - LEFT 2 VIEWS"
                           }

articles/azure-health-insights/includes/example-inference-finding-json-request.md

@@ -79,7 +79,7 @@ ms.service: azure-health-insights
                       "code": {
                         "coding": [
                           {
-                            "system": "Https://loinc.org",
+                            "system": "https://loinc.org",
                             "code": "24627-2",
                             "display": "CT CHEST"
                           }

articles/azure-health-insights/includes/example-inference-follow-up-communication-json-request.md

@@ -79,7 +79,7 @@ ms.service: azure-health-insights
                       "code": {
                         "coding": [
                           {
-                            "system": "Https://loinc.org",
+                            "system": "https://loinc.org",
                             "code": "36572-6",
                             "display": "XR CHEST AP"
                           }