Rename image folders

reference/docs-conceptual/components/vscode/How-To-Replicate-the-ISE-Experience-In-VSCode.md

@@ -28,7 +28,7 @@ Select "PowerShell: Enable ISE Mode" from the list.
 This command will apply a lot of the settings found in this document automatically.
 The result looks like this:
 
-![ISE Mode](images/How-To-Replicate-the-ISE-Experience-In-VSCode/3-ise-mode.png)
+![ISE Mode](media/How-To-Replicate-the-ISE-Experience-In-VSCode/3-ise-mode.png)
 
 The rest of this article includes more detailed information on settings in ISE Mode and
 some additional settings.
@@ -60,11 +60,11 @@ If you're looking to simplify the Visual Studio Code UI to look more closely to
 
 This will hide the "Activity Bar" and the "Debug Side Bar" sections below inside of the red box:
 
-![highlighted section includes Activity Bar and Debug Side Bar](images/How-To-Replicate-the-ISE-Experience-In-VSCode/1-highlighted-sidebar.png)
+![highlighted section includes Activity Bar and Debug Side Bar](media/How-To-Replicate-the-ISE-Experience-In-VSCode/1-highlighted-sidebar.png)
 
 The end result looks like this:
 
-![Simplified view of VS Code](images/How-To-Replicate-the-ISE-Experience-In-VSCode/2-simplified-ui.png)
+![Simplified view of VS Code](media/How-To-Replicate-the-ISE-Experience-In-VSCode/2-simplified-ui.png)
 
 ## Tab completion
 

reference/docs-conceptual/components/vscode/Using-VSCode-for-Remote-Editing-and-Debugging.md

@@ -39,7 +39,7 @@ With the PowerShell extension for VSCode started and the PowerShell Integrated C
 can type `Open-EditorFile foo.ps1` or `psedit foo.ps1` to open the local foo.ps1 file right in the
 editor.
 
-![Open-EditorFile foo.ps1 works locally](images/Using-VSCode-for-Remote-Editing-and-Debugging/1-open-local-file.png)
+![Open-EditorFile foo.ps1 works locally](media/Using-VSCode-for-Remote-Editing-and-Debugging/1-open-local-file.png)
 
 >[!NOTE]
 > The file `foo.ps1` must already exist.
@@ -48,11 +48,11 @@ From there, we can:
 
 - Add breakpoints to the gutter
 
-  ![adding breakpoint to gutter](images/Using-VSCode-for-Remote-Editing-and-Debugging/2-adding-breakpoint-gutter.png)
+  ![adding breakpoint to gutter](media/Using-VSCode-for-Remote-Editing-and-Debugging/2-adding-breakpoint-gutter.png)
 
 - Hit F5 to debug the PowerShell script.
 
-  ![debugging the PowerShell local script](images/Using-VSCode-for-Remote-Editing-and-Debugging/3-local-debug.png)
+  ![debugging the PowerShell local script](media/Using-VSCode-for-Remote-Editing-and-Debugging/3-local-debug.png)
 
 While debugging, you can interact with the debug console, check out the variables in the scope on
 the left, and all the other standard debugging tools.
@@ -77,20 +77,20 @@ Since we are going from macOS to an Ubuntu VM in Azure, we are using SSH for rem
 First, in the Integrated Console, run `Enter-PSSession`. You're connected to the remote session
 when `[<hostname>]` shows up to the left of your prompt.
 
-![The call to Enter-PSSession](images/Using-VSCode-for-Remote-Editing-and-Debugging/4-enter-pssession.png)
+![The call to Enter-PSSession](media/Using-VSCode-for-Remote-Editing-and-Debugging/4-enter-pssession.png)
 
 Now, we can do the same steps as if we are editing a local script.
 
 1. Run `Open-EditorFile test.ps1` or `psedit test.ps1` to open the remote `test.ps1` file
 
-  ![Open-EditorFile the test.ps1 file](images/Using-VSCode-for-Remote-Editing-and-Debugging/5-open-remote-file.png)
+  ![Open-EditorFile the test.ps1 file](media/Using-VSCode-for-Remote-Editing-and-Debugging/5-open-remote-file.png)
 
 1. Edit the file/set breakpoints
 
-   ![edit and set breakpoints](images/Using-VSCode-for-Remote-Editing-and-Debugging/6-set-breakpoints.png)
+   ![edit and set breakpoints](media/Using-VSCode-for-Remote-Editing-and-Debugging/6-set-breakpoints.png)
 
 1. Start debugging (F5) the remote file
 
-   ![debugging the remote file](images/Using-VSCode-for-Remote-Editing-and-Debugging/7-start-debugging.png)
+   ![debugging the remote file](media/Using-VSCode-for-Remote-Editing-and-Debugging/7-start-debugging.png)
 
 If you have any problems, you can open issues in the [GitHub repo](https://github.com/powershell/vscode-powershell).

reference/docs-conceptual/components/vscode/using-vscode.md

@@ -55,7 +55,7 @@ For traditional Windows PowerShell workloads, see [Installing Windows PowerShell
    1. The **Extensions** view opens on the Side Bar. Select the PowerShell extension from Microsoft.
       You should see a VSCode screen similar to the following image:
 
-      ![VSCode](../../images/using-vscode/vscode.png)
+      ![VSCode](media/using-vscode/vscode.png)
 
    1. Click the **Install** button on the PowerShell extension from Microsoft.
    1. After the install, you see the **Install** button turns to **Reload**. Click on **Reload**.

reference/docs-conceptual/components/web-access/install-and-use-windows-powershell-web-access.md

@@ -50,7 +50,7 @@ the See Also section.
 
 The following diagram shows how Windows PowerShell Web Access works.
 
-![Windows PowerShell Web Access diagram](images/Windows-PowerShell-Web-Access-diagram.jpg)
+![Windows PowerShell Web Access diagram](media/install-and-use-windows-powershell-web-access/Windows-PowerShell-Web-Access-diagram.jpg)
 
 ## Requirements for running Windows PowerShell Web Access
 
@@ -180,8 +180,9 @@ instruct the cmdlet to change the default site container of the web application.
 configuration options that are available for web applications, such as changing the port number or
 the Secure Sockets Layer (SSL) certificate.
 
-> **![Security Note](images/securitynote.jpeg) Security Note**
-> We strongly recommend that administrators configure the gateway to use a valid certificate that has been signed by a CA.
+> [!IMPORTANT]
+> We strongly recommend that administrators configure the gateway to use a valid certificate that
+> has been signed by a CA.
 
 #### To configure the Windows PowerShell Web Access gateway with a test certificate by using Install-PswaWebApplication
 
@@ -194,7 +195,7 @@ the Secure Sockets Layer (SSL) certificate.
 
    `Install-PswaWebApplication -UseTestCertificate`
 
-   > **![Security Note](images/securitynote.jpeg) Security Note**
+   > [!IMPORTANT]
    > The `UseTestCertificate` parameter should only be used in a private test environment. For a
    > secure production environment, we recommend using a valid certificate that has been signed by
    > a CA.
@@ -221,8 +222,9 @@ the Secure Sockets Layer (SSL) certificate.
 
    > [!NOTE]
    > You cannot sign in until users have been granted access to the website by adding authorization
-   > rules. For more information, see [configure a restrictive authorization rule](#configure-a-restrictive-authorization-rule)
-   > and [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
+   > rules. For more information, see
+   > [configure a restrictive authorization rule](#configure-a-restrictive-authorization-rule) and
+   > [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
 
 #### To configure the Windows PowerShell Web Access gateway with a genuine certificate by using Install-PswaWebApplication and IIS Manager
 
@@ -273,8 +275,10 @@ the Secure Sockets Layer (SSL) certificate.
 
    > [!NOTE]
    > You cannot sign in until users have been granted access to the website by adding authorization
-   > rules. For more information, see [Configure a restrictive authorization rule](#configure-a-restrictive-authorization-rule),
-   > in this topic, and [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
+   > rules. For more information, see
+   > [Configure a restrictive authorization rule](#configure-a-restrictive-authorization-rule), in
+   > this topic, and
+   > [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
 
 ### Configure a restrictive authorization rule
 
@@ -336,7 +340,8 @@ gateway in IIS Manager.
 1. If Server Manager is already open, go on to the next step. If Server Manager is not already
    open, open it by doing one of the following.
 
-   - On the Windows desktop, start Server Manager by clicking **Server Manager** in the Windows taskbar.
+   - On the Windows desktop, start Server Manager by clicking **Server Manager** in the Windows
+     taskbar.
    - On the Windows **Start** screen, click **Server Manager**.
 
 2. On the **Manage** menu, click **Add Roles and Features**.
@@ -418,7 +423,7 @@ gateway as a root website.
    [To configure an SSL certificate in IIS Manager](#to-configure-an-ssl-certificate-in-iis-manager)
    in this topic.
 
-10. ![Security Note](images/SecurityNote.jpeg) Optional security step:
+10. Optional security step:
 
     With the website selected in the tree pane, double-click **SSL Settings** in the content pane.
     Select **Require SSL**, and then in the **Actions** pane, click **Apply**. Optionally, in the
@@ -536,9 +541,11 @@ gateway as a root website.
    `https://<gateway_server_name>`. You should not need to add **/pswa** to the URL.
 
    > [!NOTE]
-   > You cannot sign in until users have been granted access to the website
-   > by adding authorization rules. For more information, see [Configure a restrictive authorization rule](#configure-a-restrictive-authorization-rule),
-   > in this topic, and [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
+   > You cannot sign in until users have been granted access to the website by adding authorization
+   > rules. For more information, see
+   > [Configure a restrictive authorization rule](#configure-a-restrictive-authorization-rule), in
+   > this topic, and
+   > [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
 
 ### Configuring a restrictive authorization rule
 
@@ -562,7 +569,7 @@ For more detail about Windows PowerShell Web Access authorization rules and secu
    - On the Windows **Start** screen, right-click **Windows PowerShell**, and then click
      **Run as Administrator**.
 
-1. ![Security Note](images/SecurityNote.jpeg) Optional step for restricting user access by using session configurations:
+1. Optional step for restricting user access by using session configurations:
 
    Verify that session configurations that you want to use in your rules already exist. If they
    have not yet been created, use instructions for creating session configurations in
@@ -574,7 +581,7 @@ For more detail about Windows PowerShell Web Access authorization rules and secu
 
    This authorization rule allows a specific user access to one computer on the network to which
    they typically have access, with access to a specific session configuration that is scoped to
-   the user'™s typical scripting and cmdlet needs.
+   the user'&trade;s typical scripting and cmdlet needs.
 
    In the following example, a user named `JSmith` in the `Contoso` domain is granted access to
    manage the computer `Contoso_214`, and use a session configuration named `NewAdminsOnly`.
@@ -611,9 +618,9 @@ valid SSL certificate from a CA.
      [GeoTrust](https://www.geotrust.com/). The certificate's common name must match the host header
      in the request.
 
-     For example, if the client browser requests `http://www.contoso.com/`, then the common name must
-     also be `http://www.contoso.com/`. This is the most secure and recommended option for providing
-     the Windows PowerShell Web Access gateway with a certificate.
+     For example, if the client browser requests `http://www.contoso.com/`, then the common name
+     must also be `http://www.contoso.com/`. This is the most secure and recommended option for
+     providing the Windows PowerShell Web Access gateway with a certificate.
 
    - Click **Create a Self-Signed Certificate** to create a certificate that you can use
      immediately, and have signed later by a CA if desired. Specify a friendly name for the