fixing headers, typos, content for bash, and metadata/images

Author: jluk

articles/cloud-shell/features-powershell.md

@@ -46,6 +46,7 @@ Capability to let you easily discover and navigate all Azure resources.
 
 > [!NOTE]
 > [TODO: replace old gif]
+> [TODO: note limitations of file writing etc. in Azure drive]
 
 ### Interaction with VMs
 

articles/cloud-shell/features.md

@@ -50,7 +50,7 @@ Files outside of `$Home` and machine state are not persisted across sessions.
 |Category   |Name   |
 |---|---|
 |Linux shell interpreter|Bash<br> sh               |
-|Azure tools            |[Azure CLI 2.0](https://github.com/Azure/azure-cli) and [1.0](https://github.com/Azure/azure-xplat-cli)<br> [AzCopy](https://docs.microsoft.com/azure/storage/storage-use-azcopy)<br> [Batch Shipyard](https://github.com/Azure/batch-shipyard)     |
+|Azure tools            |[Azure CLI 2.0](https://github.com/Azure/azure-cli) and [1.0](https://github.com/Azure/azure-xplat-cli)<br> [AzCopy](https://docs.microsoft.com/azure/storage/storage-use-azcopy)<br> [Batch Shipyard](https://github.com/Azure/batch-shipyard) <br>    |
 |Text editors           |vim<br> nano<br> emacs       |
 |Source control         |git                    |
 |Build tools            |make<br> maven<br> npm<br> pip         |

articles/cloud-shell/limitations.md

@@ -20,29 +20,28 @@ ms.author: juluk
 # Limitations of Azure Cloud Shell
 Azure Cloud Shell has the following known limitations:
 
-## System state and persistence
+## General Limitations
+
+### System state and persistence
 The machine that provides your Cloud Shell session is temporary, and it is recycled after your session is inactive for 20 minutes. Cloud Shell requires a file share to be mounted. As a result, your subscription must be able to set up storage resources to access Cloud Shell. Other considerations include:
 * With mounted storage, only modifications within the `clouddrive` directory are persisted. In Bash your `$Home` directory is also persisted.
 * File shares can be mounted only from within your [assigned region](persisting-shell-storage.md#mount-a-new-clouddrive).
   * In Bash, run `env` to find your region set as `ACC_LOCATION`.
 * Azure Files supports only locally redundant storage and geo-redundant storage accounts.
 
-## Browser support
+### Browser support
 Cloud Shell supports the latest versions of Microsoft Edge, Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, and Apple Safari. Safari in private mode is not supported.
 
-## Copy and paste
+### Copy and paste
 Ctrl+C and Ctrl+V do not function as copy/paste shortcuts in Cloud Shell on Windows machines, use Ctrl+Insert and Shift+Insert to copy and paste respectively. <br>
 Right-click copy-and-paste options are also available, but right-click function is subject to browser-specific clipboard access. 
 
-## For a given user, only one shell can be active
-Users can only launch one type of shell at a time, either **Bash** or **PowerShell**. However you may have multiple instances of Bash or PowerShell running at one time.
+### For a given user, only one shell can be active
+Users can only launch one type of shell at a time, either **Bash** or **PowerShell**. However, you may have multiple instances of Bash or PowerShell running at one time. Swapping between Bash or PowerShell will trigger a Cloud Shell restart which terminates existing sessions.
 
-## Usage limits
+### Usage limits
 Cloud Shell is intended for interactive use cases. As a result, any long-running non-interactive sessions are ended without warning.
 
-## Network connectivity
-Any latency in Cloud Shell is subject to local internet connectivity, Cloud Shell continues to attempt to carry out any instructions sent.
-
 ## Bash Limitations
 
 ### User permissions
@@ -64,5 +63,6 @@ PowerShell in Azure Cloud Shell could take up to 60 seconds to initialize during
 Any application (such as: git, vim, and others) that writes data to $Home will not be persisted across PowerShell sessions.  For a workaround [see here TODO]() 
 
 ## Next steps
+[Troubleshooting Cloud Shell](troubleshooting.md) <br>
 [Quickstart for Bash](quickstart.md) <br>
 [Quickstart for PowerShell](quickstart-powershell.md)

articles/cloud-shell/media/quickstart/Environment-Bash.PNG renamed to articles/cloud-shell/media/Unused/Environment-Bash.PNG

@@ -1,6 +1,6 @@
 ---
-title: Persist files in Azure Cloud Shell (Preview) | Microsoft Docs
-description: Walkthrough of how Azure Cloud Shell persists files.
+title: Persist files for PowerShell in Azure Cloud Shell (Preview) | Microsoft Docs
+description: Walkthrough of how PowerShell in Azure Cloud Shell persists files.
 services: azure
 documentationcenter: ''
 author: maertendmsft
@@ -13,23 +13,27 @@ ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: na
 ms.topic: article
-ms.date: 07/17/2017
+ms.date: 09/25/2017
 ms.author: damaerte
 ---
 [!include [features-introblock](../../includes/cloud-shell-persisting-shell-storage-introblock.md)]
 
+## How to get to clouddrive
+TODO: cd into $Home to see clouddrive
+TODO: What folders are inside of clouddrive (.pscloudshell, .module, etc.) automatically, where do modules get saved?
+
 ## How Cloud Shell works
 Cloud Shell persists files through the following method: 
 * Mounting your specified file share as `clouddrive` in your `$Home` directory for direct file-share interaction.
 
-## List Cloud Drive file shares
+## List `clouddrive`
 The `Get-CloudDrive` command retrieves the file share information currently mounted by the Cloud Drive in the Cloud Shell. <br>
 ![Running Get-CloudDrive](media/persisting-shell-storage-powershell/Get-Clouddrive.png)
 
-## Unmount Cloud Drive
+## Unmount `clouddrive`
 You can unmount a file share that's mounted to Cloud Shell at any time. If the file share has been removed, you will be prompted to create and mount a new file share at the next session.
 
-The `Dismount-CloudDrive` command unmounts a file share from the current storage account. Dismounting the Cloud Drive terminates the current session. The user will be prompted to create and mount a new file share during the next session.
+The `Dismount-CloudDrive` command unmounts a file share from the current storage account. Dismounting the Cloud Drive terminates the current session. The user will be prompted to create and mount another file share during the next session.
 ![Running Dismount-CloudDrive](media/persisting-shell-storage-powershell/Dismount-Clouddrive.png)
 
 [!include [features-endblock](../../includes/cloud-shell-persisting-shell-storage-endblock.md)]

articles/cloud-shell/media/quickstart/env-selector.png

@@ -1,6 +1,6 @@
 ---
-title: Persist files in Azure Cloud Shell (Preview) | Microsoft Docs
-description: Walkthrough of how Azure Cloud Shell persists files.
+title: Persist files for Bash in Azure Cloud Shell (Preview) | Microsoft Docs
+description: Walkthrough of how Bash in Azure Cloud Shell persists files.
 services: azure
 documentationcenter: ''
 author: jluk
@@ -13,13 +13,13 @@ ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: na
 ms.topic: article
-ms.date: 07/17/2017
+ms.date: 09/25/2017
 ms.author: juluk
 ---
 
 [!include [features-introblock](../../includes/cloud-shell-persisting-shell-storage-introblock.md)]
 
-## How Cloud Shell works 
+## How Cloud Shell storage works 
 Cloud Shell persists files through both of the following methods: 
 * Creating a disk image of your `$Home` directory to persist all contents within the directory. The disk image is saved in your specified file share as `acc_<User>.img` at `fileshare.storage.windows.net/fileshare/.cloudconsole/acc_<User>.img`, and it automatically syncs changes. 
 * Mounting your specified file share as `clouddrive` in your `$Home` directory for direct file-share interaction. `/Home/<User>/clouddrive` is mapped to `fileshare.storage.windows.net/fileshare`.
@@ -28,7 +28,7 @@ Cloud Shell persists files through both of the following methods:
 > All files in your `$Home` directory, such as SSH keys, are persisted in your user disk image, which is stored in your mounted file share. Apply best practices when you persist information in your `$Home` directory and mounted file share.
 
 ## Use the `clouddrive` command
-With Cloud Shell, you can run a command called `clouddrive`, which enables you to manually update the file share that's mounted to Cloud Shell.
+With Bash in Cloud Shell, you can run a command called `clouddrive`, which enables you to manually update the file share that is mounted to Cloud Shell.
 ![Running the "clouddrive" command](media/persisting-shell-storage/clouddrive-h.png)
 
 ## Mount a new `clouddrive`
@@ -43,7 +43,7 @@ If you mount an existing file share, the storage accounts must be:
 ### The `clouddrive mount` command
 
 > [!NOTE]
-> If you're mounting a new file share, a new user image is created for your `$Home` directory, because your previous `$Home` image is kept in the previous file share.
+> If you're mounting a new file share, a new user image is created for your `$Home` directory. Your previous `$Home` image is kept in your previous file share.
 
 Run the `clouddrive mount` command with the following parameters:
 
@@ -56,25 +56,20 @@ To view more details, run `clouddrive mount -h`, as shown here:
 ![Running the `clouddrive mount`command](media/persisting-shell-storage/mount-h.png)
 
 ## Unmount `clouddrive`
-You can unmount a file share that's mounted to Cloud Shell at any time. However, because Cloud Shell requires a mounted file share, you will be prompted to create and mount a new file share at the next session if it has been removed.
+You can unmount a file share that's mounted to Cloud Shell at any time. Since Cloud Shell requires a mounted file share to be used, you will be prompted to create and mount another file share on the next session.
 
-### The `clouddrive unmount` command
-
-To remove a file share from Cloud Shell:
 1. Run `clouddrive unmount`.
-2. Acknowledge and confirm the prompts.
-
-Your file share will continue to exist unless you delete it manually. Cloud Shell will no longer search for this file share on subsequent sessions.
+2. Acknowledge and confirm prompts.
 
-To view more details, run `clouddrive unmount -h`, as shown here:
+Your file share will continue to exist unless you delete it manually. Cloud Shell will no longer search for this file share on subsequent sessions. To view more details, run `clouddrive unmount -h`, as shown here:
 
 ![Running the `clouddrive unmount`command](media/persisting-shell-storage/unmount-h.png)
 
 > [!WARNING]
 > Although running this command will not delete any resources, manually deleting a resource group, storage account, or file share that's mapped to Cloud Shell will erase your `$Home` directory disk image and any files in your file share. This action cannot be undone.
 
-## List `clouddrive` file shares
-To discover which file share is mounted as `clouddrive`, run the following `df` command. 
+## List `clouddrive`
+To discover which file share is mounted as `clouddrive`, run the `df` command. 
 
 The file path to clouddrive will show your storage account name and file share in the URL. For example, `//storageaccountname.file.core.windows.net/filesharename`
 

articles/cloud-shell/persisting-shell-storage-powershell.md

@@ -1,9 +1,28 @@
-# PowerShell in Azure Cloud Shell quickstart
+---
+title: PowerShell in Azure Cloud Shell (Preview) quickstart | Microsoft Docs
+description: Quickstart for PowerShell in Cloud Shell
+services: 
+documentationcenter: ''
+author: maertendmsft
+manager: timlt
+tags: azure-resource-manager
+ 
+ms.assetid: 
+ms.service: azure
+ms.workload: infrastructure-services
+ms.tgt_pltfrm: vm-linux
+ms.devlang: na
+ms.topic: article
+ms.date: 09/25/2017
+ms.author: damaerte
+---
+
+# Quickstart for PowerShell in Azure Cloud Shell
 
 This document details how to use the PowerShell in Cloud Shell in the [Azure portal](https://aka.ms/PSCloudPreview).
 
 > [!NOTE]
-> A [Bash in Azure Cloud Shell](quickstart.md) guide is also available.
+> A [Bash in Azure Cloud Shell](quickstart.md) quickstart is also available.
 
 ## Start Cloud Shell
 
@@ -17,7 +36,7 @@ This document details how to use the PowerShell in Cloud Shell in the [Azure por
 
 3. Select PowerShell
 
-4. The `Azure PS drive` appears as follows
+4. The `Azure drive` appears as follows
 
   ```powershell
   Requesting a Cloud Shell... Succeeded.

articles/cloud-shell/persisting-shell-storage.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Cloud Shell (Preview) quickstart | Microsoft Docs
-description: Quickstart for Bash Cloud Shell
+title: Bash in Azure Cloud Shell (Preview) quickstart | Microsoft Docs
+description: Quickstart for Bash in Cloud Shell
 services: 
 documentationcenter: ''
 author: jluk
@@ -13,16 +13,16 @@ ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: na
 ms.topic: article
-ms.date: 08/28/2017
+ms.date: 09/25/2017
 ms.author: juluk
 ---
 
-# Quickstart for using Bash in Cloud Shell
+# Quickstart for Bash in Azure Cloud Shell
 
 This document details how to use Bash in Azure Cloud Shell in the [Azure portal](https://ms.portal.azure.com/).
 
 > [!NOTE]
-> A [PowerShell in Azure Cloud Shell](quickstart-powershell.md) guide is also available.
+> A [PowerShell in Azure Cloud Shell](quickstart-powershell.md) quickstart is also available.
 
 ## Start Cloud Shell
 1. Launch **Cloud Shell** from the top navigation of the Azure portal <br>
@@ -33,9 +33,9 @@ This document details how to use Bash in Azure Cloud Shell in the [Azure portal]
 > [!TIP]
 > You are automatically authenticated for Azure CLI 2.0 in every sesssion.
 
-### Select the Bash Environment
+### Select the Bash environment
 1. Select the environment drop down from the the left hand side of shell window <br>
-![](media/quickstart/Environment-Bash.png)
+![](media/quickstart/env-selector.png)
 2. Select Bash
 
 ### Set your subscription
@@ -74,6 +74,6 @@ Delete your resource group and any resources within it: <br>
 Run `az group delete -n MyRG`
 
 ## Next steps
-[Learn about persisting storage on Cloud Shell](persisting-shell-storage.md) <br>
+[Learn about persisting files for Bash in Cloud Shell](persisting-shell-storage.md) <br>
 [Learn about Azure CLI 2.0](https://docs.microsoft.com/cli/azure/) <br>
 [Learn about Azure File storage](../storage/files/storage-files-introduction.md) <br>

articles/cloud-shell/quickstart-powershell.md

@@ -13,16 +13,12 @@ ms.workload: infrastructure-services
 ms.tgt_pltfrm: vm-linux
 ms.devlang: na
 ms.topic: article
-ms.date: 09/05/2017
+ms.date: 09/25/2017
 ms.author: damaerte
 ---
 
 # Troubleshooting Azure Cloud Shell
-Known resolutions for issues in Azure Cloud Shell:
-
-## An error about [MissingSubscriptionRegistration](media/troubleshooting/storageRP-error.jpg) occurs during persistent storage creation
-  - **Details**: The selected subscription does not have Storage RP registered.
-  - **Resolution**: [Register your Storage resource provider](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-common-deployment-errors#noregisteredproviderfound).
+Known resolutions for issues in Azure Cloud Shell include:
 
 ## Error: 400 DisallowedOperation
  - **Details**: When using an Azure Active Directory subscription, you cannot create storage.

articles/cloud-shell/quickstart.md

@@ -1,34 +1,45 @@
 # Persist files in Azure Cloud Shell
-Cloud Shell takes advantage of Azure File storage to persist files across sessions.
+Cloud Shell utilizes of Azure File storage to persist files across sessions.
 
 ## Set up a `clouddrive` file share
 On initial start, Cloud Shell prompts you to associate a new or existing file share to persist files across sessions.
 
 > [!NOTE]
-> Bash and PowerShell share the same file share. Meaning only one file share can be associated with automatic mounting in Cloud Shell.
+> Bash and PowerShell share the same file share. Only one file share can be associated with automatic mounting in Cloud Shell.
 
 ### Create new storage
 
 When you use basic settings and select only a subscription, Cloud Shell creates three resources on your behalf in the supported region that's nearest to you:
 * Resource group: `cloud-shell-storage-<region>`
-* Storage account: `cs-uniqueGuid`
-* File share: `cs-<user>-<domain>-com-uniqueGuid`
+* Storage account: `cs<uniqueGuid>`
+* File share: `cs-<user>-<domain>-com-<uniqueGuid>`
 
 ![The Subscription setting](../articles/cloud-shell/media/persisting-shell-storage/basic-storage.png)
 
-The file share mounts as `clouddrive` in your `$Home` directory. In Bash, he file share is also used to store a 5-GB image that's created for you and that automatically updates and persists your `$Home` directory. This is a one-time action, and the file share mounts automatically in subsequent sessions.
+The file share mounts as `clouddrive` in your `$Home` directory. This is a one-time action, and the file share mounts automatically in subsequent sessions. 
+
+In Bash, the file share also contains a 5-GB image that is created for you which automatically persists data in your `$Home` directory. 
 
 ### Use existing resources
 
-By using the advanced option, you can associate existing resources. When the storage setup prompt appears, select **Show advanced settings** to view additional options. In Bash, existing file shares receive a 5-GB user image to persist your `$Home` directory. The drop-down menus are filtered for your assigned Cloud Shell region and the locally redundant storage and geo-redundant storage accounts.
+By using the advanced option, you can associate existing resources. When the storage setup prompt appears, select **Show advanced settings** to view additional options. The drop-down menus are filtered for your assigned Cloud Shell region and the locally redundant storage and geo-redundant storage accounts.
+
+In Bash, existing file shares receive a 5-GB image created for you to persist your `$Home` directory.
 
 ![The Resource group setting](../articles/cloud-shell/media/persisting-shell-storage/advanced-storage.png)
 
 ### Restrict resource creation with an Azure resource policy
 Storage accounts that you create in Cloud Shell are tagged with `ms-resource-usage:azure-cloud-shell`. If you want to disallow users from creating storage accounts in Cloud Shell, create an [Azure resource policy for tags](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-policy-tags) that are triggered by this specific tag.
 
 ## Supported storage regions
-The Azure files must reside in the same region as the Cloud Shell machine that you're mounting them to. Cloud Shell machines exist in the following regions:
+Associated Azure storage accounts must reside in the same region as the Cloud Shell machine that you're mounting them to.
+
+To find your assigned region you may:
+* View the note on the "Advanced storage settings" dialog
+* Refer to the name of the storage account created for you (ex: `cloud-shell-storage-westus`)
+* Run `env` and locate the variable `ACC_LOCATION`
+
+Cloud Shell machine exist in the following regions:
 |Area|Region|
 |---|---|
 |Americas|East US, South Central US, West US|