tweaks

Author: tamram

articles/storage/blobs/TOC.yml

@@ -154,8 +154,6 @@
       href: ../common/storage-redundancy.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
     - name: Data protection
       items:
-      - name: Point-in-time restore
-        href: point-in-time-restore-overview.md  
       - name: Versioning
         href: versioning-overview.md
       - name: Soft delete
@@ -164,6 +162,8 @@
         href: snapshots-overview.md  
       - name: Change feed
         href: storage-blob-change-feed.md
+      - name: Point-in-time restore
+        href: point-in-time-restore-overview.md  
     - name: Access and performance tiers
       items:
       - name: Access tiers
@@ -387,8 +387,6 @@
         href: ../common/geo-redundant-design.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json
     - name: Protect your data
       items:
-      - name: Enable point-in-time restore
-        href: point-in-time-restore-manage.md  
       - name: Enable blob versioning
         href: versioning-enable.md
       - name: Enable soft delete
@@ -397,6 +395,8 @@
         href: snapshots-manage-dotnet.md
       - name: Process change feed logs
         href: storage-blob-change-feed-how-to.md
+      - name: Enable point-in-time restore
+        href: point-in-time-restore-manage.md  
     - name: Manage disaster recovery
       items:
       - name: Check the Last Sync Time property

articles/storage/blobs/point-in-time-restore-manage.md

@@ -102,11 +102,11 @@ Keep in mind the following rules when specifying a range of blobs to restore:
 - The container pattern specified for the start range and end range must include a minimum of three characters. The forward slash (/) that is used to separate a container name from a blob name does not count toward this minimum.
 - Only one range can be specified per restore operation.
 - Wildcard characters are not supported. They are treated as standard characters.
-- You can restore blobs in the `$root` and `$web` containers by explicitly specifying them in a range pass to a restore operation. The `$root` and `$web` containers are not restored unless they are explicitly specified, so they are not restored when a restore operation restores all containers in the storage account. Other system containers cannot restored.
+- You can restore blobs in the `$root` and `$web` containers by explicitly specifying them in a range passed to a restore operation. The `$root` and `$web` containers are restored only if they are explicitly specified. Other system containers cannot restored.
 
 ### Restore all containers in the account
 
-To restore all containers and blobs in the storage account, call the Restore-AzStorageBlobRange command, omitting the -BlobRestoreRange parameter. The following example restores containers in the storage account to their state 12 hours before the present moment:
+To restore all containers and blobs in the storage account, call the Restore-AzStorageBlobRange command, omitting the `-BlobRestoreRange` parameter. The following example restores containers in the storage account to their state 12 hours before the present moment:
 
 ```powershell
 # Specify -TimeToRestore as a UTC value
@@ -119,13 +119,13 @@ Restore-AzStorageBlobRange -ResourceGroupName $rgName `
 
 To restore a range of blobs, call the Restore-AzStorageBlobRange command and specify a lexicographical range of container and blob names for the `-BlobRestoreRange` parameter. The start of the range is in inclusive, and the end of the range is exclusive.
 
-For example, to restore the blobs in a single container named *sample-container*, you can specify a range that starts with *sample-container* and ends with *sample-container1*. There is no requirement for the containers named in the start and end ranges to exist. Because the end of the range is exclusive, even if the storage account includes a container named *sample-container1*, only the container named *sample-container* will be restored by the restore operation:
+For example, to restore the blobs in a single container named *sample-container*, you can specify a range that starts with *sample-container* and ends with *sample-container1*. There is no requirement for the containers named in the start and end ranges to exist. Because the end of the range is exclusive, even if the storage account includes a container named *sample-container1*, only the container named *sample-container* will be restored:
 
 ```powershell
 $range = New-AzStorageBlobRangeToRestore -StartRange sample-container -EndRange sample-container1
 ```
 
-To specify a subset of blobs in a container to restore, use a forward slash (/) to separate the container name from the blob pattern. For example, the following range selects blobs in the container whose names begin with the letters *d* through *f*:
+To specify a subset of blobs in a container to restore, use a forward slash (/) to separate the container name from the blob pattern. For example, the following range selects blobs in a single container whose names begin with the letters *d* through *f*:
 
 ```powershell
 $range = New-AzStorageBlobRangeToRestore -StartRange sample-container/d -EndRange sample-container/g

articles/storage/blobs/point-in-time-restore-overview.md

@@ -28,18 +28,17 @@ Azure Storage analyzes all changes that have been made to the specified blobs be
 
 When you request a restore operation, Azure Storage blocks data operations on the blobs in the range being restored for the duration of the operation. Read, write, and delete operations are blocked in the primary location. Read operations from the secondary location may proceed during the restore operation if the storage account is geo-replicated.
 
+Only one restore operation can be run on a storage account at a time. A restore operation cannot be canceled once it is in progress, but a second restore operation can be performed to undo the first operation.
+
 To check the status of a point-in-time restore, call the **Get Restore Status** operation with the restore ID returned from the **Restore Blob Ranges** operation.
 
-Keep in mind the following points about restore operations:
+Keep in mind the following limitations on restore operations:
 
-- Only one restore operation can be run on a storage account at a time. A restore operation cannot be canceled once it is in progress, but a second restore operation can be performed to undo the first operation.
 - A block that has been uploaded via [Put Block](/rest/api/storageservices/put-block) or [Put Block from URL](/rest/api/storageservices/put-block-from-url), but not committed via [Put Block List](/rest/api/storageservices/put-block-list), is not part of a blob and so is not restored as part of a restore operation.
 - A blob with an active lease cannot be restored. If a blob with an active lease is included in the range of blobs to restore, the restore operation will fail atomically.
 - Snapshots are not created or deleted as part of a restore operation. Only the base blob is restored to its previous state.
 - If a blob has moved between the hot and cool tiers in the period between the present moment and the restore point, the blob is restored to its previous tier. However, a blob that has moved to the archive tier will not be restored.
 
-Point-in-time restore supports restoring operations on block blobs only. Operations on containers cannot be restored.
-
 > [!CAUTION]
 > Point-in-time restore supports restoring operations on block blobs only. Operations on containers cannot be restored. If you delete a container from the storage account by calling the [Delete Container](/rest/api/storageservices/delete-container) operation during the point-in-time restore preview, that container cannot be restored with a restore operation. During the preview, instead of deleting a container, delete individual blobs if you may want to restore them.
 
@@ -51,7 +50,7 @@ Point-in-time restore requires that the following Azure Storage features are ena
 - [Change feed (preview)](storage-blob-change-feed.md)
 - [Blob versioning (preview)](versioning-overview.md)
 
-Enable these features for the storage account before you enable point-in-time restore. Be sure to register for the change feed preview before you enable it.
+Enable these features for the storage account before you enable point-in-time restore. Be sure to register for the change feed and blob versioning previews before you enable them.
 
 ### Retention period for point-in-time restore