Merge pull request #57176 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/azure-resource-manager/resource-group-template-functions-resource.md

@@ -114,11 +114,10 @@ The following [example template](https://github.com/Azure/azure-docs-json-sample
             "type": "string",
             "defaultValue": "southcentralus"
         },
-        "requestContent": {
+        "accountSasProperties": {
             "type": "object",
             "defaultValue": {
                 "signedServices": "b",
-                "signedResourceType": "c",
                 "signedPermission": "r",
                 "signedExpiry": "2018-08-20T11:00:00Z",
                 "signedResourceTypes": "s"
@@ -160,7 +159,7 @@ The following [example template](https://github.com/Azure/azure-docs-json-sample
         },
         "accountSAS": {
             "type": "object",
-            "value": "[listAccountSas(parameters('storagename'), '2018-02-01', parameters('requestContent'))]"
+            "value": "[listAccountSas(parameters('storagename'), '2018-02-01', parameters('accountSasProperties'))]"
         }
     }
 }

articles/service-fabric-mesh/service-fabric-mesh-faq.md

@@ -21,7 +21,7 @@ Ask questions, get answers from Microsoft engineers, and report issues in the [s
 
 **What is the cost of participating in the preview?**
 
-There are no charges for deploying applications or containers to the Mesh preview currently. However,  we encourage you to to delete the resources you deploy and not leave them running unless you're actively testing them.
+There are no charges for deploying applications or containers to the Mesh preview currently. However,  we encourage you to delete the resources you deploy and not leave them running unless you're actively testing them.
 
 **Is there a quota limit of the number of cores and RAM?**
 

articles/site-recovery/vmware-azure-manage-configuration-server.md

@@ -1,6 +1,6 @@
 ---
 title: Manage the configuration server for VMware and physical server disaster recovery with Azure Site Recovery | Microsoft Docs
-description: This article describes how to manage an existing configuration server for disaster recovery of VMware VMs and physical servers to Azure with Azure Site RecoveryS.
+description: This article describes how to manage an existing configuration server for disaster recovery of VMware VMs and physical servers to Azure with Azure Site Recovery.
 author: rayne-wiselman
 manager: carmonm
 ms.service: site-recovery
@@ -133,10 +133,10 @@ You run update rollups to update the configuration server. Updates can be applie
 - If you run 9.7, 9.8, 9.9, or 9.10, you can upgrade directly to 9.11.
 - If you run 9.6 or earlier and you want to upgrade to 9.11, you must first upgrade to version 9.7. before 9.11.
 
-Links to update rollups for upgrading to all versions of the configuration server are available in the [wiki updates page](https://social.technet.microsoft.com/wiki/contents/articles/38544.azure-site-recovery-service-updates.aspx).
+Links to update rollups for upgrading to all versions of the configuration server are available in the [Azure updates page](https://azure.microsoft.com/updates/?product=site-recovery).
 
 > [!IMPORTANT]
-> With every new version 'N' of an Azure Site Recovery componenet that is released, all versions below 'N-4' is considered out of support. It is always advisable to upgrade to the latest versions available.
+> With every new version 'N' of an Azure Site Recovery component that is released, all versions below 'N-4' is considered out of support. It is always advisable to upgrade to the latest versions available.
 
 Upgrade the server as follows: