Some acrolinx

Author: MikeRayMSFT

docs/database-engine/configure-windows/configure-pmem.md

@@ -25,11 +25,11 @@ This article describes how to configure the persistent memory (PMEM) for [!INCLU
 
 ### Create namespaces for PMEM devices
 
-In Windows, use the `ipmctl` utility to configure the PMEM disks (referred to as namespaces in Linux). You can find Intel® Optane™ specific instructions [here](https://www.intel.com/content/www/us/en/developer/articles/guide/qsg-part3-windows-provisioning-with-optane-pmem.html). Details on supported PMEM hardware on different Windows versions is provided [here](/azure-stack/hci/concepts/deploy-persistent-memory#supported-hardware). PMEM disks should be interleaved across PMEM NVDIMMs and can provide different types of user-space access to memory regions on the device. For more on interleaved sets in Windows see [here](/azure-stack/hci/concepts/deploy-persistent-memory#understand-interleaved-sets).
+In Windows, use the `ipmctl` utility to configure the PMEM disks (referred to as namespaces in Linux). You can find Intel® Optane™ specific instructions [here](https://www.intel.com/content/www/us/en/developer/articles/guide/qsg-part3-windows-provisioning-with-optane-pmem.html). Details on supported PMEM hardware on different Windows versions are at [Understand and deploy persistent memory](/azure-stack/hci/concepts/deploy-persistent-memory#supported-hardware). PMEM disks should be interleaved across PMEM NVDIMMs and can provide different types of user-space access to memory regions on the device. For more on interleaved sets in Windows see [here](/azure-stack/hci/concepts/deploy-persistent-memory#understand-interleaved-sets).
 
 ## PMEM disks
 
-### Using powershell to examine PMEM disks
+### Use PowerShell to examine PMEM disks
 
 ```powershell
 #Get information about all physical disks
@@ -44,16 +44,19 @@ Get-PmemPhysicalDevice
 #Get information about unused PMEM regions
 Get-PmemUnusedRegion
 ```
+
 ### BTT and DAX
 
 By default, `New-PmemDisk` will use the desired `FSDax` mode. Atomicity is set to the default of `None` rather than `BlockTranslationTable`. From a support perspective, BTT must be enabled for the transaction log, to mimic required sector mode semantics. Although use of [BTT](/azure-stack/hci/concepts/deploy-persistent-memory#block-translation-table) with NTFS is generally recommended, BTT is not recommended when using large pages, such as required for [DAX](/windows-server/storage/storage-spaces/persistent-memory-direct-access#dax-and-block-translation-table-btt).
 
 ```powershell
 Get-PmemUnusedRegion | New-PmemDisk -Atomicity None
 ```
+
 ### Formatting the NTFS volume(s)
 
 ```powershell
+
 #Initialize PMEM Disk(s)
 Get-PmemDisk | Initialize-Disk -PartitionStyle GPT
 
@@ -72,20 +75,24 @@ Format-Volume `
 ## File alignment and offset
 
 ### Check partition offset(s)
+
 ```powershell
 Get-Partition | Select-Object DiskNumber, DriveLetter, IsDAX, Offset, Size, PartitionNumber | fl
 ```
-We can check the file alignment of a particular file using `fsutil`. Note that our file size must be a modulo of 2MB.
+
+Check the file alignment of a particular file using `fsutil`. Note that our file size must be a modulo of 2 MB.
+
 ```bash
 fsutil dax queryFileAlignment A:\AdventureWorks2019_A.mdf
 ```
+
 ## Replacing PMEM
 
 ### Reprovision PMEM disks
 
-Whenever a PMEM module is replaced it needs to be reprovisioned.
+Whenever a PMEM module is replaced, it needs to be re-provisioned.
 
-> [!Note]
+> [!NOTE]
 > Removing a PMEM disk will result in the loss of data on that disk.
 
 ```powershell
@@ -94,10 +101,13 @@ Get-PmemDisk | Remove-PmemDisk -Confirm:$false
 ```
 ### Erase PMEM modules
 
-To permanently erase data from PMEM modules use the `Initialize-PmemPhysicalDevice` powershell cmdlet.
+To permanently erase data from PMEM modules use the `Initialize-PmemPhysicalDevice` PowerShell cmdlet.
 
 ```powershell
 # Reinitialize all PMEM disks
 Get-PmemPhysicalDevice | Initialize-PmemPhysicalDevice -Confirm:$false
 ```
-Other powershell cmdlets for manipulating PMEM are listed [here](/powershell/module/persistentmemory/).
+
+## See also
+
+For other cmdlets for manipulating PMEM see [PersistentMemory](/powershell/module/persistentmemory/) in the PowerShell reference documentation.

docs/relational-databases/databases/add-persisted-log-buffer.md

@@ -1,5 +1,5 @@
 ---
-description: "Add persisted log buffer to a database"
+description: "Explains how to add a persisted log buffer to a database in SQL Server 2019 and later. Provides Transact SQL examples."
 title: "Add persisted log buffer to a database"
 ms.custom: ""
 ms.date: "10/30/2019"
@@ -18,7 +18,7 @@ helpviewer_keywords:
 ms.assetid: 8ead516a-1334-4f40-84b2-509d0a8ffa45
 author: "briancarrig"
 ms.author: "brcarrig"
-manager: amitban
+ms.reviewer: mikeray
 ---
 
 # Add persisted log buffer to a database
@@ -40,7 +40,7 @@ To configure a persistent memory device in [Windows](../../database-engine/confi
 
 ## Add a persisted log buffer to a database  
 
-The following examples adds a persisted log buffer.
+The following example adds a persisted log buffer.
 
 ```sql
 ALTER DATABASE <MyDB> 
@@ -64,15 +64,15 @@ ALTER DATABASE WideWorldImporters
   );
 ```
 
-Note that the log file on the DAX volume will be sized at 20MB regardless of the size specified wih the ADD FILE command.
+The log file on the DAX volume will be sized at 20 MB regardless of the size specified with the ADD FILE command.
 
 The volume or mount the new log file is placed must be formatted with DAX enabled (NTFS) or mounted with the DAX option (XFS/EXT4).
 
 ## Remove a persisted log buffer
 
 To safely remove a persisted log buffer, the database must be placed in single user mode in order to drain the persisted log buffer.
 
-The following example places removes a persisted log buffer.
+The following example removes a persisted log buffer.
 
 ```sql
 ALTER DATABASE <MyDB> SET SINGLE_USER;
@@ -93,13 +93,13 @@ ALTER DATABASE WideWorldImporters SET MULTI_USER;
 
 [Availability Groups](../../t-sql/statements/create-availability-group-transact-sql.md) can only use this feature on secondary replicas due to the requirement by the log reader agent for standard log writing semantics on the primary. However, the small log file must be created on all nodes (ideally on DAX volumes or mounts). In the event of a failover, the persisted log buffer path must exist, in order for the failover to be successful.
 
-In cases where the path or file are not present during an Availability Group failover event, or database startup, the database will enter a `RECOVERY PENDING` state until the issue is resolved.
+In cases where the path or file isn't present during an Availability Group failover event, or database startup, the database enters a `RECOVERY PENDING` state until the issue is resolved.
 
 ## Interoperability with other PMEM features
 
 When both Persisted log buffer and [Hybrid Buffer Pool](../../database-engine/configure-windows/hybrid-buffer-pool.md) are jointly enabled, along with start-up [trace flag 809](../../t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql.md), Hybrid buffer pool will operate in what is known as _Direct Write_ mode.
 
-## Backup and restore operations
+## Back up and restore operations
 
 Normal restore conditions apply. If persisted log buffer is restored to a DAX volume or mount, it will continue to function, otherwise it can be safely removed.