Merge pull request #300850 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/cdn/cdn-overview.md

@@ -39,7 +39,7 @@ For a list of current content delivery network node locations, see [Azure Conten
 
 3. The origin server returns the file to an edge server in the POP.
 
-4. An edge server in the POP caches the file and returns the file to the original requestor (Alice). The file remains cached on the edge server in the POP until the time to live (TTL) specified by its HTTP headers expires. If the origin server didn't specify a TTL, the default TTL is seven days.
+4. An edge server in the POP caches the file and returns the file to the original requester (Alice). The file remains cached on the edge server in the POP until the time to live (TTL) specified by its HTTP headers expires. If the origin server didn't specify a TTL, the default TTL is seven days.
 
 5. More users can then request the same file by using the same URL that Alice used, and gets directed to the same POP.
 

articles/cdn/cdn-standard-rules-engine-actions.md

@@ -86,7 +86,7 @@ Use this action to redirect clients to a new URL.
 
 Field | Description
 ------|------------
-Type | Select the response type to return to the requestor: Found (302), Moved (301), Temporary redirect (307), and Permanent redirect (308).
+Type | Select the response type to return to the requester: Found (302), Moved (301), Temporary redirect (307), and Permanent redirect (308).
 Protocol | Match Request, HTTP, HTTPS.
 Hostname | Select the host name you want the request to be redirected to. Leave blank to preserve the incoming host.
 Path | Define the path to use in the redirect. Leave blank to preserve the incoming path.

articles/frontdoor/front-door-rules-engine-actions.md

@@ -359,7 +359,7 @@ Use the **URL redirect** action to redirect clients to a new URL. Clients are se
 
 | Property | Supported values |
 |----------|------------------|
-| Redirect type | The response type to return to the requestor. <ul><li>In the Azure portal: Found (302), Moved (301), Temporary Redirect (307), Permanent Redirect (308).</li><li>In ARM templates: `Found`, `Moved`, `TemporaryRedirect`, `PermanentRedirect`</li></ul> |
+| Redirect type | The response type to return to the requester. <ul><li>In the Azure portal: Found (302), Moved (301), Temporary Redirect (307), Permanent Redirect (308).</li><li>In ARM templates: `Found`, `Moved`, `TemporaryRedirect`, `PermanentRedirect`</li></ul> |
 | Redirect protocol | <ul><li>In the Azure portal: `Match Request`, `HTTP`, `HTTPS`</li><li>In ARM templates: `MatchRequest`, `Http`, `Https`</li></ul> |
 | Destination host | The host name you want the request to be redirected to. Leave blank to preserve the incoming host. |
 | Destination path | The path to use in the redirect. Include the leading `/`. Leave blank to preserve the incoming path. |

articles/internet-peering/faqs.md

@@ -29,7 +29,7 @@ Peering connections that were set up outside of the automated portal process and
 
 ### When will peering IP addresses be allocated and displayed in the Azure portal?
 
-Our automated process allocates IP addresses and sends the information via email to the PNI requestor after the port is configured on our side. This may take up to a week after the request has been submitted as the port has been cabled before it can be configured.
+Our automated process allocates IP addresses and sends the information via email to the PNI requester after the port is configured on our side. This may take up to a week after the request has been submitted as the port has been cabled before it can be configured.
 
 ### What Microsoft routes will be advertised over Peering Service connections?
 

articles/web-application-firewall/afds/waf-sensitive-data-protection-configure-frontdoor.md

@@ -29,7 +29,7 @@ The following table shows examples of log scrubbing rules that can be used to pr
 
 <sup>1</sup> If a request triggers a rule that scans the request body, and the content type is either `application/x-www-form-urlencoded` or `application/json`,  the WAF will scrub all request details from the logs to prevent any potential storage of PII. 
 
-<sup>2</sup> Request IP Address and Request URI rules only support the *equals any* operator and scrubs all instances of the requestor's IP address that appears in the WAF logs.
+<sup>2</sup> Request IP Address and Request URI rules only support the *equals any* operator and scrubs all instances of the requester's IP address that appears in the WAF logs.
 
 For more information, see [What is Azure Web Application Firewall on Azure Front Door Sensitive Data Protection?](waf-sensitive-data-protection-frontdoor.md)
 

articles/web-application-firewall/ag/waf-sensitive-data-protection-configure.md

@@ -29,7 +29,7 @@ The following table shows examples of log scrubbing rules that can be used to pr
 | Request JSON Arg Names | Equals | Jsonarg | "data":"Matched Data: ****** found within ARGS:jsonarg: ******" |
 | Request IP Address* | Equals Any | NULL | "clientIp":"******" |
 
-\* Request IP Address rules only support the *equals any* operator and scrubs all instances of the requestor's IP address that appears in the WAF logs.
+\* Request IP Address rules only support the *equals any* operator and scrubs all instances of the requester's IP address that appears in the WAF logs.
 
 For more information, see [What is Azure Web Application Firewall Sensitive Data Protection?](waf-sensitive-data-protection.md)