feedback changes

sipastak · sipastak · commit 881bc6943a4d · 2023-02-14T09:03:03.000-05:00
diff --git a/articles/import-export/storage-import-export-data-from-blobs.md b/articles/import-export/storage-import-export-data-from-blobs.md
@@ -5,7 +5,7 @@ author: alkohli
 services: storage
 ms.service: azure-import-export
 ms.topic: tutorial
-ms.date: 03/14/2022
+ms.date: 02/13/2023
 ms.author: alkohli
 ms.custom: "tutorial, devx-track-azurepowershell, devx-track-azurecli, contperf-fy21q3"
 ---
@@ -42,7 +42,7 @@ You must:
 
 # [Portal](#tab/azure-portal-preview)
 
-Perform the following steps to order an import job in Azure Import/Export. The Azure Import/Export service will create a job of the type "Data Box."
+Perform the following steps to order an import job in Azure Import/Export. The Azure Import/Export service creates a job of the type "Data Box."
 
 1. Use your Microsoft Azure credentials to sign in at this URL: [https://portal.azure.com](https://portal.azure.com).
 1. Select **+ Create a resource** and search for *Azure Data Box*. Select **Azure Data Box**.
@@ -104,7 +104,7 @@ Perform the following steps to order an import job in Azure Import/Export. The A
         <Blob selections include a container, a blob, and blob prefixes that work like wildcards. The Add Prefixes pane on the right is used to add prefixes that select blobs based on common text in the blob path or name.>
 :::image-end:::
 
-    - Choose **Export from blob list file (XML format)**, and select an XML file that contains a list of paths and prefixes for the blobs to be exported from the storage account. You must construct the XML file and store it in a container for the storage account. The file cannot be empty.
+    - Choose **Export from blob list file (XML format)**, and select an XML file that contains a list of paths and prefixes for the blobs to be exported from the storage account. You must construct the XML file and store it in a container for the storage account. The file can't be empty.
 
       > [!IMPORTANT]
       > If you use an XML file to select the blobs to export, make sure that the XML contains valid paths and/or prefixes. If the file is invalid or no data matches the paths specified, the order terminates with partial data or no data exported.
@@ -121,7 +121,7 @@ Perform the following steps to order an import job in Azure Import/Export. The A
 1. In **Return shipping**:
 
    1. Select a shipping carrier from the drop-down list for **Carrier**. The location of the Microsoft datacenter for the selected region determines which carriers are available.
-   1. Enter a **Carrier account number**. The account number for an valid carrier account is required.
+   1. Enter a **Carrier account number**. The account number for a valid carrier account is required.
    1. In the **Return address** area, use **+ Add Address** to add the address to ship to.
 
       ![Screenshot of the Return Shipping tab for an import job in Azure Data Box. The Return Shipping tab and the Plus Add Address button are highlighted.](./media/storage-import-export-data-from-blobs/import-export-order-preview-07-export-job.png)
@@ -324,7 +324,7 @@ Install-Module -Name Az.ImportExport
 
 ## Step 2: Ship the drives
 
-If you do not know the number of drives you need, see [Determine how many drives you need](storage-import-export-determine-drives-for-export.md#determine-how-many-drives-you-need). If you know the number of drives, proceed to ship the drives.
+If you don't know the number of drives you need, see [Determine how many drives you need](storage-import-export-determine-drives-for-export.md#determine-how-many-drives-you-need). If you know the number of drives, proceed to ship the drives.
 
 [!INCLUDE [storage-import-export-ship-drives](../../includes/storage-import-export-ship-drives.md)]
 
@@ -336,8 +336,8 @@ If you do not know the number of drives you need, see [Determine how many drives
 
 When the dashboard reports the job is complete, the disks are shipped to you and the tracking number for the shipment is available in the portal.
 
-1. After you receive the drives with exported data, you need to get the BitLocker keys to unlock the drives. Go to the export job in the Azure portal. Click **Import/Export** tab.
-2. Select and click your export job from the list. Go to **Encryption** and copy the keys.
+1. After you receive the drives with exported data, you need to get the BitLocker keys to unlock the drives. Go to the export job in the Azure portal. Select **Import/Export** tab.
+2. Select your export job from the list. Go to **Encryption** and copy the keys.
 
    ![Screenshot of the Encryption blade for an export job in Azure Import Export Jobs. The Encryption menu item and Copy button for the key are highlighted.](./media/storage-import-export-data-from-blobs/export-from-blob-7.png)
 
@@ -351,7 +351,7 @@ Use the following command to unlock the drive:
 
    `WAImportExport Unlock /bk:<BitLocker key (base 64 string) copied from Encryption blade in Azure portal> /driveLetter:<Drive letter>`
 
-Here is an example of the sample input.
+Here's an example of the sample input.
 
    `WAImportExport.exe Unlock /bk:CAAcwBoAG8AdQBsAGQAIABiAGUAIABoAGkAZABkAGUAbgA= /driveLetter:e`
 
diff --git a/articles/import-export/storage-import-export-data-to-blobs.md b/articles/import-export/storage-import-export-data-to-blobs.md
@@ -49,13 +49,13 @@ This step generates a journal file. The journal file stores basic information su
 Perform the following steps to prepare the drives.
 
 1. Connect your disk drives to the Windows system via SATA connectors.
-2. Create a single NTFS volume on each drive. Assign a drive letter to the volume. Do not use mountpoints.
+2. Create a single NTFS volume on each drive. Assign a drive letter to the volume. Don't use mountpoints.
 3. Enable BitLocker encryption on the NTFS volume. If using a Windows Server system, use the instructions in [How to enable BitLocker on Windows Server 2012 R2](https://thesolving.com/storage/how-to-enable-bitlocker-on-windows-server-2012-r2/).
 4. Copy data to encrypted volume. Use drag and drop or Robocopy or any such copy tool. A journal (*.jrn*) file is created in the same folder where you run the tool.
 
    If the drive is locked and you need to unlock the drive, the steps to unlock may be different depending on your use case.
 
-   * If you have added data to a pre-encrypted drive (WAImportExport tool was not used for encryption), use the BitLocker key (a numerical password that you specify) in the popup to unlock the drive.
+   * If you have added data to a pre-encrypted drive (WAImportExport tool wasn't used for encryption), use the BitLocker key (a numerical password that you specify) in the popup to unlock the drive.
 
    * If you have added data to a drive that was encrypted by WAImportExport tool, use the following command to unlock the drive:
 
@@ -85,9 +85,9 @@ Perform the following steps to prepare the drives.
     |/bk:     |The BitLocker key for the drive. Its numerical password from output of `manage-bde -protectors -get D:`      |
     |/srcdir:     |The drive letter of the disk to be shipped followed by `:\`. For example, `D:\`.         |
     |/dstdir:     |The name of the destination container in Azure Storage.         |
-    |/blobtype:     |This option specifies the type of blobs you want to import the data to. For block blobs, the blob type is `BlockBlob` and for page blobs, it is `PageBlob`.         |
-    |/skipwrite:     | Specifies that there is no new data required to be copied and existing data on the disk is to be prepared.          |
-    |/enablecontentmd5:     |The option when enabled, ensures that MD5 is computed and set as `Content-md5` property on each blob. Use this option only if you want to use the `Content-md5` field after the data is uploaded to Azure. <br> This option does not affect the data integrity check (that occurs by default). The setting does increase the time taken to upload data to cloud.          |
+    |/blobtype:     |This option specifies the type of blobs you want to import the data to. For block blobs, the blob type is `BlockBlob` and for page blobs, it's `PageBlob`.         |
+    |/skipwrite:     | Specifies that there's no new data required to be copied and existing data on the disk is to be prepared.          |
+    |/enablecontentmd5:     |The option when enabled, ensures that MD5 is computed and set as `Content-md5` property on each blob. Use this option only if you want to use the `Content-md5` field after the data is uploaded to Azure. <br> This option doesn't affect the data integrity check (that occurs by default). The setting does increase the time taken to upload data to cloud.          |
 
     > [!NOTE]
     > - If you import a blob with the same name as an existing blob in the destination container, the imported blob will overwrite the existing blob. In earlier tool versions (before 1.5.0.300), the imported blob was renamed by default, and a \Disposition parameter let you specify whether to rename, overwrite, or disregard the blob in the import.
@@ -97,7 +97,7 @@ Perform the following steps to prepare the drives.
 
    A journal file with the provided name is created for every run of the command line. 
 
-   Together with the journal file, a `<Journal file name>_DriveInfo_<Drive serial ID>.xml` file is also created in the same folder where the tool resides. The .xml file is used in place of the journal file when creating a job if the journal file is too big.
+   Together with the journal file, a `<Journal file name>_DriveInfo_<Drive serial ID>.xml` file is also created in the same folder where the tool resides. The .xml file is used in place of the journal file when creating a job if the journal file is too large.
 
 > [!IMPORTANT]
 > * Do not modify the journal files or the data on the disk drives, and don't reformat any disks, after completing disk preparation.
diff --git a/articles/import-export/storage-import-export-data-to-files.md b/articles/import-export/storage-import-export-data-to-files.md
@@ -5,15 +5,15 @@ author: alkohli
 services: storage
 ms.service: azure-import-export
 ms.topic: tutorial
-ms.date: 02/01/2023
+ms.date: 02/13/2023
 ms.author: alkohli
 ms.custom: "tutorial, devx-track-azurepowershell, devx-track-azurecli, contperf-fy21q3"
 ---
 # Tutorial: Transfer data to Azure Files with Azure Import/Export
 
 This article provides step-by-step instructions on how to use the Azure Import/Export service to securely import large amounts of data into Azure Files. To import data, the service requires you to ship supported disk drives containing your data to an Azure datacenter.
 
-The Import/Export service supports only import of Azure Files into Azure Storage. Exporting Azure Files is not supported.
+The Import/Export service supports only import of Azure Files into Azure Storage. Exporting Azure Files isn't supported.
 
 In this tutorial, you learn how to:
 
@@ -51,7 +51,7 @@ Do the following steps to prepare the drives.
 2. Create a single NTFS volume on each drive. Assign a drive letter to the volume. Do not use mountpoints.
 3. Modify the *dataset.csv* file in the root folder where the tool is. Depending on whether you want to import a file or folder or both, add entries in the *dataset.csv* file similar to the following examples.
 
-   - **To import a file**: In the following example, the data to copy is on the F: drive. Your file *MyFile1.txt*  is copied to the root of the *MyAzureFileshare1*. If the *MyAzureFileshare1* does not exist, it's created in the Azure Storage account. Folder structure is maintained.
+   - **To import a file**: In the following example, the data to copy is on the F: drive. Your file *MyFile1.txt*  is copied to the root of the *MyAzureFileshare1*. If the *MyAzureFileshare1* doesn't exist, it's created in the Azure Storage account. Folder structure is maintained.
 
        ```
            BasePath,DstItemPathOrPrefix,ItemType
@@ -65,7 +65,7 @@ Do the following steps to prepare the drives.
        ```
    
        > [!NOTE]
-       > The /Disposition parameter, which let you choose what to do when you import a file that already exists in earlier versions of the tool, is not supported in Azure Import/Export version 2.2.0.300. In the earlier tool versions, an imported file with the same name as an existing file was renamed by default.
+       > The /Disposition parameter, which let you choose what to do when you import a file that already exists in earlier versions of the tool, isn't supported in Azure Import/Export version 2.2.0.300. In the earlier tool versions, an imported file with the same name as an existing file was renamed by default.
 
      Multiple entries can be made in the same file corresponding to folders or files that are imported.
 
@@ -78,7 +78,7 @@ Do the following steps to prepare the drives.
 
     This example assumes that two disks are attached and basic NTFS volumes G:\ and H:\ are created. H:\is not encrypted while G: is already encrypted. The tool formats and encrypts the disk that hosts H:\ only (and not G:\).
 
-   - **For a disk that is not encrypted**: Specify *Encrypt* to enable BitLocker encryption on the disk.
+   - **For a disk that isn't encrypted**: Specify *Encrypt* to enable BitLocker encryption on the disk.
 
        ```
        DriveLetter,FormatOption,SilentOrPromptOnFormat,Encryption,ExistingBitLockerKey
diff --git a/includes/storage-import-export-update-job-tracking.md b/includes/storage-import-export-update-job-tracking.md
@@ -6,7 +6,7 @@ services: storage
 
 ms.service: storage
 ms.topic: include
-ms.date: 11/18/2021
+ms.date: 02/13/2023
 ms.author: alkohli
 ms.custom: include file
 ---
@@ -18,9 +18,9 @@ After you provide tracking details, the job status changes to Shipping, and the
 > [!IMPORTANT]
 > If the tracking number is not updated within 2 weeks of creating the job, the job expires. 
 
-### [Portal (Preview)](#tab/azure-portal-preview)
+### [Portal](#tab/azure-portal-preview)
 
-To complete the tracking information for a job that you created in the Preview portal, do these steps:
+To complete the tracking information for a job that you created in the portal, do these steps:
  
 1. Open the job in the [Azure portal/](https://portal.azure.com/).
 1. On the **Overview** pane, scroll down to **Tracking information** and complete the entries: 
@@ -36,22 +36,6 @@ You can track the job progress on the **Overview** pane. For a description of ea
 ![Screenshot showing status tracking on the Overview pane for an Azure Import Export job in the Preview portal.](./media/storage-import-export-update-job-tracking/import-export-order-tracking-info-02.png)
 
 
-### [Portal (Classic)](#tab/azure-portal-classic)
-
-To complete the tracking information for a job that you created in the Classic portal, do these steps.
- 
-1. Open the job in the [Azure portal/](https://portal.azure.com/).
-1. At the top of the ****For job to progress, provide the tracking information** to open the **Update status** pane. Then complete the entries: 
-    
-    1. Select the checkbox by **Mark as shipped**.
-    1. Provide the **Carrier** and **Tracking number**.
-    1. When you finish, select **Save**.
-
-    ![!Screenshot of tracking information on the Overview pane for an Azure Import Export job as it appears in the Classic portal. Current job status, Tracking Information area, and Update button are highlighted.](./media/storage-import-export-update-job-tracking/import-export-order-tracking-info-classic-01.png)
-
-You can track the job progress on the **Overview** pane. For a description of each job state, go to [View your job status](../articles/import-export/storage-import-export-view-drive-status.md).
-
-
 ### [Azure CLI](#tab/azure-cli)
 
 If you created your Azure Import/Export job using Azure CLI, open the job in the Azure portal to update tracking information. Azure CLI and Azure PowerShell create jobs in the classic Azure Import/Export service and hence create an Azure resource of the type "Import/Export job."
