Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs into FromPublicRepo

Author: huypub

articles/log-analytics/log-analytics-containers.md

@@ -524,7 +524,7 @@ You can verify that the Container Monitoring solution is set correctly for Windo
 
 ## Solution components
 
-If you are using Windows agents, then the following management pack is installed on each computer with an agent when you add this solution. No configuration or maintenance is required for the management pack.
+From the OMS portal, navigate to the *Solutions Gallery* and add the **Container Monitoring Solution**. If you are using Windows agents, then the following management pack is installed on each computer with an agent when you add this solution. No configuration or maintenance is required for the management pack.
 
 - *ContainerManagement.xxx* installed in C:\Program Files\Microsoft Monitoring Agent\Agent\Health Service State\Management Packs
 
@@ -560,6 +560,7 @@ Labels appended to *PodLabel* data types are your own custom labels. The appende
 ## Monitor containers
 After you have the solution enabled in the Log Analytics portal, the **Containers** tile shows summary information about your container hosts and the containers running in hosts.
 
+
 ![Containers tile](./media/log-analytics-containers/containers-title.png)
 
 The tile shows an overview of how many containers you have in the environment and whether they're failed, running, or stopped.

articles/marketplace/marketplace-publishers-guide.md

@@ -74,12 +74,12 @@ Each storefront offers specialized publishing options to help you maximize your
 ## How to Publish on Cloud Marketplace
 
 Becoming a cloud marketplace publisher is an easy three-step process:
-1.	Determine the listing type right for your offer
+1.	Choose a publishing option for your offer
 2.	Sign up to become a cloud marketplace publisher
 3.	Complete technical and content pre-requisites required by offer and listing type
 
 
-**1.	Determine the Listing Type Right for Your Offer**
+**1.	Choose a publishing option for your offer**
 
 Each storefront supports multiple publishing options and offer types. Select an offer type that best represents your application and service details. All publishing options will give partners access to lead sharing.
 

articles/service-fabric/service-fabric-cluster-capacity.md

@@ -67,9 +67,9 @@ The durability tier is used to indicate to the system the privileges that your V
 
 This privilege is expressed in the following values:
 
-* Gold - The infrastructure jobs can be paused for a duration of two hours per UD. Gold durability can be enabled only on full-node VM SKUs like L32s, GS5, G5, DS15_v2, D15_v2. In general, all the VM Sizes listed at http://aka.ms/vmspecs that are marked as 'Instance is isolated to hardware dedicated to a single customer' in the note, are full-node VMs.
-* Silver - The infrastructure Jobs can be paused for a duration of 10 minutes per UD and is available on all standard VMs of single core and above.
-* Bronze - No privileges. This is the default. Only use this durability level for Node Types that run _only_ stateless workloads. 
+* Gold - Updates you make to your VMSS can be delayed until approved by the Service Fabric cluster. Updates and maintenance initiated by Azure can be delayed for up two hours, allowing additional time for replicas to recover from earlier failures. Gold durability can be enabled only on full-node VM sizes like L32s, GS5, G5, DS15_v2, D15_v2. In general, all the VM sizes listed at http://aka.ms/vmspecs that are marked as 'Instance is isolated to hardware dedicated to a single customer' in the note are full-node VMs.
+* Silver - Updates you make to your VMSS can be delayed until approved by the Service Fabric cluster. Updates and maintenance initiated by Azure cannot be delayed for any significant period of time. Silver durability is available on all standard VMs of single core and above.
+* Bronze - This is the default. Updates and maintenance affecting your VMs will not be delayed by the Service Fabric cluster.
 
 > [!WARNING]
 > NodeTypes running with Bronze durability obtain _no privileges_. This means that infrastructure jobs that impact your stateless workloads will not be stopped or delayed. It is possible that such jobs can still impact your workloads, causing downtime or other issues. For any sort of production workload, running with at least Silver is recommended. You must maintain a minimum count of five nodes for any node-type that has a durability of Gold or Silver. 
@@ -108,10 +108,11 @@ Use Silver or Gold durability for all node types that host stateful services you
     > Changing the VM SKU Size for virtual machine scale sets not running at least Silver durability is not recommended. Changing VM SKU Size is a data-destructive in-place infrastructure operation. Without at least some ability to delay or monitor this change, it is possible that the operation can cause data loss for stateful services or cause other unforeseen operational issues, even for stateless workloads. 
     > 
 
-- Maintain a minimum count of five nodes for any virtual machine scale set that has durability level of Gold or Silver enabled
+- Maintain a minimum count of five nodes for any virtual machine scale set that has durability level of Gold or Silver enabled.
+- Each VM scale set with durability level Silver or Gold must map to its own node type in the Service Fabric cluster. Mapping multiple VM scale sets to a single node type will prevent coordination between the Service Fabric cluster and the Azure infrastructure from working properly.
 - Do not delete random VM instances, always use virtual machine scale set scale down feature. The deletion of random VM instances has a potential of creating imbalances in the VM instance spread across UD and FD. This imbalance could adversely affect the systems ability to properly load balance amongst the service instances/Service replicas.
 - If using Autoscale, then set the rules such that scale in (removing of VM instances) are done only one node at a time. Scaling down more than one instance at a time is not safe.
-- If Scaling down a primary node type, you should never scale it down more than what the reliability tier allows.
+- If deleting or deallocating VMs on the primary node type, you should never reduce the count of allocated VMs below what the reliability tier requires. These operations will be blocked indefinitely in a scale set with a durability level of Silver or Gold.
 
 ## The reliability characteristics of the cluster
 The reliability tier is used to set the number of replicas of the system services that you want to run in this cluster on the primary node type. The more the number of replicas, the more reliable the system services are in your cluster.