Merge pull request #182939 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 1cb026b1f5a6 · 2021-12-15T14:53:11.000-08:00
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/azure-docs (branch master)
diff --git a/articles/azure-functions/functions-run-local.md b/articles/azure-functions/functions-run-local.md
@@ -149,7 +149,6 @@ Version 1.x of the Core Tools isn't supported on macOS. Use version 2.x or a lat
 5. Install the Core Tools package:
 
     ```bash
-    sudo apt-get update
     sudo apt-get install azure-functions-core-tools-4
     ```
 
@@ -160,7 +159,6 @@ Version 1.x of the Core Tools isn't supported on macOS. Use version 2.x or a lat
 5. Install the Core Tools package:
 
     ```bash
-    sudo apt-get update
     sudo apt-get install azure-functions-core-tools-3
     ```
 
@@ -171,7 +169,6 @@ Version 1.x of the Core Tools isn't supported on macOS. Use version 2.x or a lat
 5. Install the Core Tools package:
 
     ```bash
-    sudo apt-get update
     sudo apt-get install azure-functions-core-tools-2
     ```
 
diff --git a/articles/azure-resource-manager/bicep/install.md b/articles/azure-resource-manager/bicep/install.md
@@ -31,7 +31,7 @@ If you get an error during installation, see [Troubleshoot Bicep installation](i
 
 ## Deployment environment
 
-After setting up your development environment, you need to install Bicep CLI for your deployment environment. Depends on whether you want to use [Azure CLI](#azure-cli) or [Azure PowerShell](#azure-powershell), the steps to set up a local deployment environment are different. Those steps are shown in the next sections.
+After setting up your development environment, you need to install Bicep CLI for your deployment environment. Depending on whether you want to use [Azure CLI](#azure-cli) or [Azure PowerShell](#azure-powershell), the steps to set up a local deployment environment are different. Those steps are shown in the next sections.
 
 To deploy Bicep files from an Azure Pipeline, see [Integrate Bicep with Azure Pipelines](add-template-to-azure-pipelines.md). To deploy Bicep files through GitHub Actions, see [Deploy Bicep files by using GitHub Actions](deploy-github-actions.md).
 
@@ -49,7 +49,7 @@ To verify your current version, run:
 az --version
 ```
 
-You now have everything you need to [deploy](deploy-cli.md) and [decompile](decompile.md) Bicep files. You have everything because Azure CLI automatically installs the Bicep CLI when a command is executed that needs it.
+You now have everything you need to [deploy](deploy-cli.md) and [decompile](decompile.md) Bicep files. Azure CLI will automatically install the Bicep CLI when a command is executed that needs it.
 
 To manually start the Bicep CLI installation, use:
 
diff --git a/articles/cognitive-services/personalizer/concept-multi-slot-personalization.md b/articles/cognitive-services/personalizer/concept-multi-slot-personalization.md
@@ -38,7 +38,7 @@ Whenever you display products and/or content to users, you may want to show more
 * **Search results or lists**: If your application search functionality, where you provide results as lists or tiles, you can use multi-slot personalization to choose which items to highlight at the top considering more metadata than traditional rankers.
 * **Dynamic channels and playlists**: Multi-slot personalization can help determine a short sequence for a list of videos or songs to play next in a dynamic channel.
 
-Multi-slot personalization allows you to declare the "slots" in the user interface that actions need to be chosen for. It also allows you to provide more information about the slots, that Personalizer can use to improve product placement - such as is this a big box or a small box? does it display a caption or only a feature? is it in a footer or a sidebar?.
+Multi-slot personalization allows you to declare the "slots" in the user interface that actions need to be chosen for. It also allows you to provide more information about the slots so that Personalizer can use to improve product placement - such as is this a big box or a small box? Does it display a caption or only a feature? Is it in a footer or a sidebar?
 
 
 ## How to use Multi-slot personalization 
diff --git a/articles/data-share/supported-data-stores.md b/articles/data-share/supported-data-stores.md
@@ -17,8 +17,8 @@ In this article, you'll learn about the rich set of Azure data stores that Azure
 
 The following table explains the data stores that Azure Data Share supports. 
 
-| Data store | Sharing based on full snapshots | Sharing based on incremental snapshots | Sharing in place 
-|:--- |:--- |:--- |:--- |:--- |:--- |:--- |
+| Data store | Sharing based on full snapshots | Sharing based on incremental snapshots | Sharing in place |
+|:--- |:--- |:--- |:--- |
 | Azure Blob Storage |✓ |✓ | |
 | Azure Data Lake Storage Gen1 |✓ |✓ | |
 | Azure Data Lake Storage Gen2 |✓ |✓ ||
@@ -50,6 +50,8 @@ When file systems, containers, or folders are shared in snapshot-based sharing,
 
 An incremental snapshot is based on the last-modified time of the files. Existing files that have the same name as files in the received data are overwritten in a snapshot. Files that are deleted from the source aren't deleted on the target. 
 
+If a snapshot is interrupted and fails, for example, due to a cancel action, networking issue, or disaster, the next incremental snapshot copies files that have a last-modified time greater than the time of the last successful snapshot.
+
 For more information, see [Share and receive data from Azure Blob Storage and Azure Data Lake Storage](how-to-share-from-storage.md).
 
 ## Share from a SQL-based source
@@ -59,6 +61,8 @@ Data consumers can choose to accept the data into Azure Data Lake Storage Gen2 o
 
 When consumers accept data into Azure Data Lake Storage Gen2 or Azure Blob Storage, full snapshots overwrite the contents of the target file if the file already exists. When data is received into a table and the target table doesn't already exist, Azure Data Share creates an SQL table by using the source schema. If a target table already exists and it has the same name, it's dropped and overwritten with the latest full snapshot. Incremental snapshots aren't currently supported.
 
+If a snapshot is interrupted and fails, for example, due to a cancel action, networking issue, or disaster, the next snapshot copies the entire table or view again.
+
 For more information, see [Share and receive data from Azure SQL Database and Azure Synapse Analytics](how-to-share-from-sql.md).
 
 ## Share from Data Explorer
diff --git a/articles/virtual-desktop/language-packs.md b/articles/virtual-desktop/language-packs.md
@@ -38,7 +38,7 @@ You need the following things to customize your Windows 10 Enterprise multi-sess
         - [Windows 10, version 1903 or 1909 Inbox Apps ISO](https://software-download.microsoft.com/download/pr/18362.1.190318-1202.19h1_release_amd64fre_InboxApps.iso)
         - [Windows 10, version 2004 Inbox Apps ISO](https://software-download.microsoft.com/download/pr/19041.1.191206-1406.vb_release_amd64fre_InboxApps.iso)
         - [Windows 10, version 20H2 Inbox Apps ISO](https://software-download.microsoft.com/download/pr/19041.508.200905-1327.vb_release_svc_prod1_amd64fre_InboxApps.iso)
-        - [Windows 10, version 21H1 Inbox Apps ISO](https://software-download.microsoft.com/download/sg/19041.928.210407-2138.vb_release_svc_prod1_amd64fre_InboxApps.iso)
+        - [Windows 10, version 21H1 or 21H2 Inbox Apps ISO](https://software-download.microsoft.com/download/sg/19041.928.210407-2138.vb_release_svc_prod1_amd64fre_InboxApps.iso)
      
      - If you use Local Experience Pack (LXP) ISO files to localize your images, you will also need to download the appropriate LXP ISO for the best language experience
         - If you're using Windows 10, version 1903 or 1909:
diff --git a/articles/virtual-desktop/overview.md b/articles/virtual-desktop/overview.md
@@ -117,8 +117,8 @@ To learn more about URLs you must unblock to use the clients, see the [Safe URL
 
 Azure Virtual Desktop follows the [Microsoft Lifecycle Policy](/lifecycle/) and supports the following x64 operating system images:
 
-* Windows 11 Enterprise multi-session (Preview)
-* Windows 11 Enterprise (Preview)
+* Windows 11 Enterprise multi-session
+* Windows 11 Enterprise
 * Windows 10 Enterprise multi-session
 * Windows 10 Enterprise
 * Windows 7 Enterprise
@@ -133,8 +133,8 @@ Available automation and deployment options depend on which OS and version you c
 
 |Operating system|Azure Image Gallery|Manual VM deployment|Azure Resource Manager template integration|Provision host pools on Azure Marketplace|
 |--------------------------------------|:------:|:------:|:------:|:------:|
-|Windows 11 Enterprise multi-session (Preview)|Yes|Yes|Yes|Yes|
-|Windows 11 Enterprise (Preview)|Yes|Yes|Yes|Yes|
+|Windows 11 Enterprise multi-session|Yes|Yes|Yes|Yes|
+|Windows 11 Enterprise|Yes|Yes|Yes|Yes|
 |Windows 10 Enterprise multi-session, version 1909 and later|Yes|Yes|Yes|Yes|
 |Windows 10 Enterprise, version 1909 and later|Yes|Yes|Yes|Yes|
 |Windows 7 Enterprise|Yes|Yes|No|No|
