Merge pull request #6128 from MicrosoftDocs/master

6/5 PM Publish

Author: huypub

docs/linux/sql-server-linux-availability-group-failover-ha.md

@@ -66,7 +66,7 @@ During a manual failover, the `pcs` command `move` or `crm` command `migrate` ad
 - **RHEL/Ubuntu example**
 
    ```bash
-   sudo pcs constraint --full
+   sudo pcs constraint list --full
    ```
 
 - **SLES example**
@@ -75,35 +75,17 @@ During a manual failover, the `pcs` command `move` or `crm` command `migrate` ad
    crm config show
    ```
 
-Remove the location constraint so future failovers - including automatic failover - succeed. 
-
-To remove the constraint, run the following command: 
+An example of the constraint which gets created becuase of a manual failover. 
+ `Enabled on: Node1 (score:INFINITY) (role: Master) (id:cli-prefer-ag_cluster-master)`
 
 - **RHEL/Ubuntu example**
 
-   In this example `ag_cluster-master` is the name of the resource that failed over. 
-
-   ```bash
-   sudo pcs resource clear ag_cluster-master 
-   ```
-
-- **SLES example**
-
-   In this example `ag_cluster` is the name of the resource that failed over. 
-
-   ```bash
-   crm resource clear ag_cluster
-   ```
-
-Alternatively, you can run the following command to remove the location constraint.  
-
-- **RHEL/Ubuntu example**
-
-   In the following command `cli-prefer-ag_cluster-master` is the ID of the constraint that needs to be removed. `sudo pcs constraint --full` returns this ID. 
-
+   In the following command `cli-prefer-ag_cluster-master` is the ID of the constraint that needs to be removed. `sudo pcs constraint list --full` returns this ID. 
+   
    ```bash
    sudo pcs constraint remove cli-prefer-ag_cluster-master  
    ```
+   
 - **SLES example**
 
    In the following command `cli-prefer-ms-ag_cluster` is the ID of the constraint. `crm config show` returns this ID. 

docs/relational-databases/blob/remote-blob-store-rbs-sql-server.md

@@ -37,7 +37,7 @@ manager: craigg
 ### Efficient BLOB management  
  Several RBS features support stored BLOBs management:  
 
--   BLOBS are managed with ACID (atomic consistency isolation durable) transactions.  
+-   BLOBS are managed with ACID (atomic, consistent, isolatable, durable) transactions.  
 
 -   BLOBs are organized into collections.  
 

docs/relational-databases/databases/revert-a-database-to-a-database-snapshot.md

@@ -39,15 +39,15 @@ manager: craigg
 ###  <a name="Restrictions"></a> Limitations and Restrictions  
  Reverting is unsupported under the following conditions:  
 
--   The database must currently have only one database snapshot, to which you plan to revert.  
+-   There are multiple snapshots for the database. For reverting, there must only be one snapshot for the database, to which you plan to revert.  
 
 -   Any read-only or compressed filegroups exist in the database.  
 
 -   Any files are now offline but were online when the snapshot was created.  
 
  Before reverting a database, consider the following limitations:  
 
--   Reverting is not intended for media recovery. . A database snapshot is an incomplete copy of the database files, so if either the database or the database snapshot is corrupted, reverting from a snapshot is likely to be impossible. Furthermore, even when it is possible, reverting in the event of corruption is unlikely to correct the problem. Therefore, taking regular backups and testing your restore plan are essential to protect a database. For more information, see [Back Up and Restore of SQL Server Databases](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md).  
+-   Reverting is not intended for media recovery. A database snapshot is an incomplete copy of the database files, so if either the database or the database snapshot is corrupted, reverting from a snapshot is likely to be impossible. Furthermore, even when it is possible, reverting in the event of corruption is unlikely to correct the problem. Therefore, taking regular backups and testing your restore plan are essential to protect a database. For more information, see [Back Up and Restore of SQL Server Databases](../../relational-databases/backup-restore/back-up-and-restore-of-sql-server-databases.md).  
 
     > [!NOTE]  
     >  If you need to be able to restore the source database to the point in time at which you created a database snapshot, use the full recovery model and implement a backup policy that enables you to do that.