Merge pull request #299856 from craxal/dev/cralvord/doc-owner

Update endpoint references and document owners

Author: denrea

articles/storage/common/storage-explorer-blob-versioning.md

@@ -2,17 +2,18 @@
 title: Azure Storage Explorer blob versioning guide
 description: Blob versioning guidance for Azure Storage Explorer
 services: storage
-author: JasonYeMSFT
+author: jinglouMSFT
 ms.service: azure-storage
 ms.subservice: storage-common-concepts
 ms.topic: concept-article
 ms.date: 08/19/2020
-ms.author: chuye
+ms.author: jinglou
+ms.reviewer: cralvord,richardgao
 ---
 
 # Azure Storage Explorer blob versioning guide
 
-Microsoft Azure Storage Explorer provides easy access and management of blob versions. This guide will help you understand how blob versioning works in Storage Explorer. Before continuing, it's recommended you read more about [blob versioning](../blobs/versioning-overview.md).
+Microsoft Azure Storage Explorer provides easy access and management of blob versions. This guide helps you understand how blob versioning works in Storage Explorer. Before continuing, we recommended you read more about [blob versioning](../blobs/versioning-overview.md).
 
 ## Terminology
 
@@ -74,7 +75,7 @@ In this view, Storage Explorer displays:
 For blobs that don't have a current version, Storage Explorer displays their latest previous version as a representation of that blob.
 
 > [!NOTE]
-> Due to service limitation, Storage Explorer needs some additional processing to get a hierarchical view of your virtual directories when listing blob versions. It will take longer to list blobs in the following views:
+> Due to service limitations, Storage Explorer needs extra processing to get a hierarchical view of your virtual directories when listing blob versions. It takes longer to list blobs in the following views:
 >
 > - Active blobs and blobs without current version
 > - All blobs and blobs without current version
@@ -89,19 +90,19 @@ Storage Explorer provides a **Manage Versions** command to view all the versions
 
 To download one or more blob versions, select the blob versions you want to download and select **Download** from the toolbar or the context menu.
 
-If you're downloading multiple versions of a blob, the downloaded files will have their version IDs at the beginning of their file names.
+If you're downloading multiple versions of a blob, the downloaded files have their version IDs at the beginning of their file names.
 
 ### Delete blob versions
 
 To delete one or more blob versions, select the blob versions you want to delete and select **Delete** from the toolbar or the context menu.
 
-Blob versions are subject to your soft-delete policy. If soft-delete is enabled, blob versions will be soft-deleted. One special case is deleting a current version. Deleting a current version will automatically make it become an active previous version instead.
+Blob versions are subject to your soft-delete policy. If soft-delete is enabled, blob versions are soft deleted. One special case is deleting a current version. Deleting a current version automatically makes it become an active previous version instead.
 
 ### Promote blob version
 
 You can restore the contents of a blob by promoting a previous version to become the current version. Select the blob version you want to promote and select **Promote Version** from the toolbar or the context menu.
 
-Non-version blobs will be overwritten by the promoted blob version. Make sure you no longer need that data or back up the data yourself before confirming the operation. Current versions automatically become previous versions, so Storage Explorer won't prompt for confirmation.
+Promoted blob versions overwrite non-version blobs. Make sure you no longer need that data or back up the data yourself before confirming the operation. Current versions automatically become previous versions, so Storage Explorer doesn't ask for confirmation.
 
 ### Undelete blob version
 

articles/storage/common/storage-explorer-command-line-options.md

@@ -2,12 +2,13 @@
 title: Azure Storage Explorer command-line options
 description: Documentation of Azure Storage Explorer start-up command-line options
 services: storage
-author: JasonYeMSFT
+author: jinglouMSFT
 ms.service: azure-storage
 ms.subservice: storage-common-concepts
 ms.topic: article
 ms.date: 02/24/2021
-ms.author: chuye
+ms.author: jinglou
+ms.reviewer: cralvord,richardgao
 ---
 
 # Azure Storage Explorer command-line options
@@ -16,15 +17,15 @@ Microsoft Azure Storage Explorer has a set of command-line options that can be a
 
 ## Command-line options
 
-Option  | Description
-:------- | :-----------
-`--debug`/`--prod`  | Start the application in debug or production mode. In debug mode, the local attachment data will be stored in the application's local storage and it won't be encrypted. Hidden properties will be displayed in the Properties panel for selected resource nodes. Log verbosity level will be set to print debug messages revealing Storage Explorer's internal setup logic. The default value is `--prod`.
-`--lang`  | Start the application with a given language. For example, `--lang="zh-Hans"`.
-`--disable-gpu` | Start the application without GPU acceleration.
-`--auto-open-dev-tools` | Let the application open the developer tools window as soon as the browser window shows. This option is useful when you want to hit a break point at a line in the start-up code of the browser window.
-`--verbosity` | Set the verbosity level of Storage Explorer logging. Supported verbosity levels include `debug`, `verbose`, `info`, `warn`, `error`, and `silent`. For example, `--verbosity=verbose`. When running in production mode, the default verbosity level is `info`. When running in debug mode, the log verbosity level will always be `debug`.
-`--log-dir` | Set the directory to save log files. For example, `--log-dir=path_to_a_directory`.
-`--ignore-certificate-errors` | Tell Storage Explorer to ignore certificate errors. This flag can be useful when you need to work in a trusted proxy environment with non-public Certificate Authority. We recommend you to [use system proxy (preview)](./storage-explorer-network.md#use-system-proxy) in such proxy environments and only set this flag if the system proxy doesn't work.
+| Option                       | Description
+|:-----------------------------|:-----------
+|`--debug`<br/>`--prod`        | Start the application in debug or production mode. In debug mode, the local attachment data is stored in the application's local storage and isn't encrypted. Hidden properties are displayed in the Properties panel for selected resource nodes. Log verbosity level is set to print debug messages revealing Storage Explorer's internal setup logic. The default value is `--prod`.
+|`--lang`                      | Start the application with a given language. For example, `--lang="zh-Hans"`.
+|`--disable-gpu`               | Start the application without GPU acceleration.
+|`--auto-open-dev-tools`       | Let the application open the developer tools window as soon as the browser window shows. This option is useful when you want to hit a break point at a line in the start-up code of the browser window.
+|`--verbosity`                 | Set the verbosity level of Storage Explorer logging. Supported verbosity levels include `debug`, `verbose`, `info`, `warn`, `error`, and `silent`. For example, `--verbosity=verbose`. When in production mode, the default verbosity level is `info`. When in debug mode, the log verbosity level is `debug`.
+|`--log-dir`                   | Set the directory to save log files. For example, `--log-dir=path_to_a_directory`.
+|`--ignore-certificate-errors` | Ignore certificate errors. This flag can be useful when you need to work in a trusted proxy environment with nonpublic Certificate Authority. We recommend you to [use system proxy (preview)](./storage-explorer-network.md#use-system-proxy) in such proxy environments and only set this flag if the system proxy doesn't work.
 
 An example of starting Storage Explorer with custom command-line options
 
@@ -33,7 +34,7 @@ An example of starting Storage Explorer with custom command-line options
 ```
 
 > [!NOTE]
-> These command line options may change in new Storage Explorer versions.
+> These command line options might change in new Storage Explorer versions.
 
 ## When to use command-line options
 

articles/storage/common/storage-explorer-direct-link.md

@@ -2,17 +2,18 @@
 title: Azure Storage Explorer direct link
 description: Documentation of Azure Storage Explorer direct link
 services: storage
-author: JasonYeMSFT
+author: jinglouMSFT
 ms.service: azure-storage
 ms.subservice: storage-common-concepts
 ms.topic: article
 ms.date: 02/24/2021
-ms.author: chuye
+ms.author: jinglou
+ms.reviewer: cralvord,richardgao
 ---
 
 # Azure Storage Explorer direct link
 
-On Windows and macOS, Storage Explorer supports URIs with the `storageexplorer://` protocol. These URIs are referred to as direct links. A direct link points to an Azure Storage resource in Storage Explorer. Following a direct link will open Storage Explorer and navigate to the resource it points to. This article describes how direct links work and how you can use them.
+On Windows and macOS, Storage Explorer supports URLs with the `storageexplorer://` protocol. These URLs are referred to as direct links. A direct link points to an Azure Storage resource in Storage Explorer. Following a direct link opens Storage Explorer and navigate to the resource it points to. This article describes how direct links work and how you can use them.
 
 ## How direct links work
 
@@ -25,19 +26,26 @@ Storage Explorer uses the tree view to visualize resources in Azure. A direct li
 
 A Storage Explorer direct link always starts with protocol `storageexplorer://`. The following table explains each of the possible parameters in a direct link.
 
-Parameter | Description
-:---------| :---------
-`v`         | Version of the direct link protocol.
-`accountid` | The Azure Resource Manager resource ID of the storage account for the linked resource. If the linked resource is a storage account, this ID will be the Azure Resource Manager resource ID of that storage account. Otherwise, this ID will be the Azure Resource Manager resource ID of the storage account the linked resource belongs to.
-`resourcetype` | Optional. Only used when the linked resource is a blob container, a file share, a queue, or a table. Must be either one of "Azure.BlobContainer", "Azure.FileShare", "Azure.Queue", "Azure.Table".
-`resourcename` | Optional. Only used when the linked resource is a blob container, a file share, a queue, or a table. The name of the linked resource.
+| Parameter      | Description
+|:---------------|:-----------
+| `v`            | Version of the direct link protocol.
+| `accountid`    | The Azure Resource Manager resource ID of the storage account for the linked resource. If the linked resource is a storage account, this ID is the Azure Resource Manager resource ID of that storage account. Otherwise, the ID is the Azure Resource Manager resource ID of the storage account the linked resource belongs to.
+| `resourcetype` | Optional. Only used when the linked resource is a blob container, a file share, a queue, or a table. Must be either one of `Azure.BlobContainer`, `Azure.FileShare`, `Azure.Queue`, or `Azure.Table`.
+| `resourcename` | Optional. Only used when the linked resource is a blob container, a file share, a queue, or a table. The name of the linked resource.
 
-Here is an example direct link to a blob container. 
-`storageexplorer://v=1&accountid=/subscriptions/the_subscription_id/resourceGroups/the_resource_group_name/providers/Microsoft.Storage/storageAccounts/the_storage_account_name&subscriptionid=the_subscription_id&resourcetype=Azure.BlobContainer&resourcename=the_blob_container_name`
+Here's an example direct link to a blob container:
+
+```
+storageexplorer://v=1
+&accountid=/subscriptions/the_subscription_id/resourceGroups/the_resource_group_name/providers/Microsoft.Storage/storageAccounts/the_storage_account_name
+&subscriptionid=the_subscription_id
+&resourcetype=Azure.BlobContainer
+&resourcename=the_blob_container_name
+```
 
 ## Get a direct link from Storage Explorer
 
-You can use Storage Explorer to get a direct link for a resource. Open the context menu of the node for the resource in the tree view. Then use the "Copy Direct Link" action to copy its direct link to the clipboard.
+You can use Storage Explorer to get a direct link for a resource. Open the context menu of the node for the resource in the tree view. Then copy its direct link to the clipboard using the "Copy Direct Link" action.
 
 ## Direct link limitations
 

articles/storage/common/storage-explorer-emulators.md

@@ -2,12 +2,13 @@
 title: Connect an emulator to Azure Storage Explorer
 description: Documentation on using an emulator with Azure Storage Explorer
 services: storage
-author: MRayermannMSFT
+author: jinglouMSFT
 ms.service: azure-storage
 ms.subservice: storage-common-concepts
 ms.topic: article
 ms.date: 11/23/2021
-ms.author: marayerm
+ms.author: jinglou
+ms.reviewer: cralvord,richardgao
 ---
 
 # Connect an emulator to Storage Explorer
@@ -16,38 +17,38 @@ Storage Explorer can be connected to an Azure Storage emulator to aid in develop
 
 ## Supported emulators
 
-Storage Explorer officially supports and recommends using [Azurite](./storage-use-azurite.md). Azurite is a cross platform, open-source emulator made by Microsoft. It supports blobs, queues, and tables. However, any emulator that functions similarly to Azurite will also likely work with Storage Explorer. Also note that Storage Explorer doesn't ship with an emulator. You'll need to download an emulator on your own.
+Storage Explorer officially supports and recommends using [Azurite](./storage-use-azurite.md). Azurite is a cross platform, open-source emulator made by Microsoft. It supports blobs, queues, and tables. However, any emulator that functions similarly to Azurite can also work with Storage Explorer. Also note that Storage Explorer doesn't ship with an emulator. You need to download an emulator on your own.
 
 ## How to connect to an emulator
 
-Before you can connect Storage Explorer to an emulator, you must first start the emulator. Storage Explorer doesn't start your emulator for you. If you attempt to access an emulator storage account before starting your emulator, you'll receive a message reminding you to start your emulator. If you attempt to access an emulator container, queue, or table, before starting your emulator you'll receive an error message.
+Before you can connect Storage Explorer to an emulator, you must first start the emulator. Storage Explorer doesn't start your emulator for you. If you attempt to access an emulator storage account before starting your emulator, a message reminds you to start your emulator. If you attempt to access an emulator container, queue, or table, before starting your emulator, you receive an error message.
 
-Assuming you have started your emulator and it is:
-- Running locally
-- Configured to listen on the typical default ports of:
+Storage Explorer automatically connects to your emulator if the following conditions are true:
+- The emulator is running locally.
+- The emulator is configured to listen on the default ports:
     - Blobs: `10000`
     - Queues: `10001`
     - Tables: `10002`
-- Configured to use HTTP
+- The emulator is configured to use HTTP
 
 Then you can quickly access your emulator resources by navigating in the resource tree view to **Local & Attached** > **Storage Accounts** > **Emulator (Default Ports)**.
 
-If any of the above aren't true, then you'll need to manually add a connection to your emulator.
+If any of the conditions aren't true, then you need to manually add a connection to your emulator.
 
 ## Manually connect to an emulator
 
 ### Local emulator
 
-If you need to manually connect to an emulator that is running locally, open the Connect dialog (plug icon in the left side) and choose **Local storage emulator**. Then fill out all required fields. Make sure to set the ports for each service type to their appropriate values. If your emulator is configured to use HTTPS, also make sure to check the checkbox for HTTPS. After you finish connecting, you can find the storage account node for your emulator under  **Local & Attached** > **Storage Accounts**.
+If you need to manually connect to an emulator that is running locally, open the "Connect" dialog (plug icon in the vertical toolbar) and choose **Local storage emulator**. Then fill out all required fields. Make sure to set the ports for each service type to their appropriate values. If your emulator is configured to use HTTPS, also make sure to check the checkbox for HTTPS. After you finish connecting, you can find the storage account node for your emulator under  **Local & Attached** > **Storage Accounts**.
 
 ### Remote emulator
 
 > [!NOTE]
-> Although Storage Explorer supports connecting to a remote emulator, it is not recommended. Certain remote emulator configurations may make it difficult for Storage Explorer to understand that an emulator is being connected to, which may affect some features. For best results, configure your emulator to use the default development account name and key, and then use a name and key connection string to connect.
+> Connecting Storage Explorer to a remote emulator isn't recommended. Certain remote emulator configurations might make it difficult for Storage Explorer to recognize these as emulator connections, which might affect some features. For best results, configure your emulator to use the default development account name and key, and then use a name and key connection string to connect.
 
-If you need to manually connect to an emulator running on a different machine, then you will need to construct a connection string that details how to connect to your emulator. The connection string will likely need to explicitly define the endpoint for each service type.
+If you need to manually connect to an emulator running on a different machine, then you need to construct a connection string that details how to connect to your emulator. The connection string likely needs to explicitly define the endpoint for each service type.
 
-Once you have a connection string, open the Connect dialog (plug icon in the left side) and choose **Storage account or service**. Then select the **Connection string** option, proceed to the next page, and use your connection string to complete the connection process. You can then find the storage account node for your emulator under **Local & Attached** > **Storage Accounts**.
+Once you have a connection string, open the "Connect" dialog (plug icon in the vertical toolbar) and choose **Storage account or service**. Then select the **Connection string** option, proceed to the next page, and use your connection string to complete the connection process. You can then find the storage account node for your emulator under **Local & Attached** > **Storage Accounts**.
 
 ## Next steps