MicrosoftDocs · learn-build-service-prod · Aug 26, 2024 · Aug 26, 2024 · Aug 26, 2024 · Aug 26, 2024
diff --git a/docs/azure/vs-azure-tools-emulator-express-debug-run.md b/docs/azure/vs-azure-tools-emulator-express-debug-run.md
@@ -27,7 +27,7 @@ When you create an Azure project, Emulator Express is automatically used. For ex
 
     ![Properties for an Azure cloud service project](./media/vs-azure-tools-emulator-express-debug-run/web-properties.png)
 
-1. Under **Local Development Server**, select **Use IIS Express option**.
+1. Under **Local Development Server**, select **Use Internet Information Services (IIS) Express option**.
 
 1. Under **Emulator**, select **Use Emulator Express**.
 

diff --git a/docs/containers/hosting-web-apps-in-docker.md b/docs/containers/hosting-web-apps-in-docker.md
@@ -17,7 +17,7 @@ ms.author: ghogen
 Docker is a lightweight container engine, similar in some ways to a virtual machine, which you can use to host applications and services.
 This tutorial walks you through using Visual Studio to publish your containerized application to an [Azure Container Registry](https://azure.microsoft.com/products/container-registry).
 
-If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?icid=dotnet?utm_source=acr-publish-doc&utm_medium=docs&utm_campaign=docs) before you begin.           
+If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/pricing/purchase-options/azure-account?icid=dotnet?utm_source=acr-publish-doc&utm_medium=docs&utm_campaign=docs) before you begin.
 
 ## Prerequisites
 
@@ -75,7 +75,7 @@ The following steps guide you through creating a basic ASP.NET Core app that you
    | **[SKU](/azure/container-registry/container-registry-skus)** | "Standard" | Select the service tier of the container registry. |
    | **Registry Location** | A nearby location | Choose a location in a [region](https://azure.microsoft.com/explore/global-infrastructure/geographies/) close to you or close to other services that you expect to use the container registry. |
 
-   :::image type="content" source="media/hosting-web-apps-in-docker/vs-azure-container-registry-provisioning-dialog-2019.png" border="false" alt-text="Screenshot that shows how to enter values in the dialog to create a new Azure Container Registry.":::
+   :::image type="content" source="media/hosting-web-apps-in-docker/vs-azure-container-registry-provisioning-dialog-2019.png" border="false" alt-text="Screenshot that shows how to enter values in the dialog to create a new Azure container registry.":::
 
 1. After you enter the resource values, select **Create**.
 
@@ -109,7 +109,7 @@ The following steps guide you through creating a basic ASP.NET Core app that you
    | **[SKU](/azure/container-registry/container-registry-skus)** | "Standard" | Select the service tier of the container registry. |
    | **Registry Location** | A nearby location | Choose a location in a [region](https://azure.microsoft.com/explore/global-infrastructure/geographies/) close to you or close to other services that you expect to use the container registry. |
 
-   :::image type="content" source="media/container-tools/vs-2022/vs-azure-container-registry-provisioning-dialog.png" border="false" alt-text="Screenshot that shows how to enter values in the dialog to create a new Azure Container Registry.":::
+   :::image type="content" source="media/container-tools/vs-2022/vs-azure-container-registry-provisioning-dialog.png" border="false" alt-text="Screenshot that shows how to enter values in the dialog to create a new Azure container registry.":::
 
 1. After you enter the resource values, select **Create**.
 

diff --git a/docs/debugger/configure-the-windows-firewall-for-remote-debugging.md b/docs/debugger/configure-the-windows-firewall-for-remote-debugging.md
@@ -94,7 +94,7 @@ If you select **Use Managed Compatibility Mode** under **Tools** > **Options** >
 
 ::: moniker-end
 
-If your domain policy requires network communication to be performed through Internet Protocol Security (IPSec), you must open additional ports on both the Visual Studio and remote computers. To debug on a remote IIS web server, open port 80 on the remote computer.
+If your domain policy requires network communication to be performed through Internet Protocol Security (IPSec), you must open additional ports on both the Visual Studio and remote computers. To debug on a remote Internet Information Services (IIS) web server, open port 80 on the remote computer.
 
 |**Ports**|**Incoming/Outgoing**|**Protocol**|**Description**|
 |-|-|-|-|

diff --git a/docs/debugger/debug-interface-access/cv-sourcechksum-t.md b/docs/debugger/debug-interface-access/cv-sourcechksum-t.md
@@ -33,7 +33,7 @@ enum CV_SourceChksum_t
 
 |Checksum Type|Value|CryptoAPI Label|Description|
 |-------------|-----|---------------|-----------|
-| `CHKSUM_TYPE_NONE` | 0 | \<none\> | No checksum present. |
+| `CHKSUM_TYPE_NONE` | 0 | <none\> | No checksum present. |
 | `CHKSUM_TYPE_MD5` | 1 | `CALG_MD5` | Checksum generated with the MD5 hashing algorithm. |
 | `CHKSUM_TYPE_SHA1` | 2 | `CALG_SHA1` | Checksum generated with the SHA1 hashing algorithm. |
 | `CHKSUM_TYPE_SHA_256` | 3 |`CALG_SHA_256`| Checksum generated with the 256-bit SHA hashing algorithm.|

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-addressoffset.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-addressoffset.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves the offset part of the contribution's address."
+description: Retrieves the offset part of the contribution's address.
 title: "IDiaSectionContrib::get_addressOffset"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_addressOffset
 
 Retrieves the offset part of the contribution's address.
 
 ## Syntax
 
 ```C++
-HRESULT get_addressOffset ( 
+HRESULT get_addressOffset ( 
    DWORD* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-addresssection.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-addresssection.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves the section part of the contribution's address."
+description: Retrieves the section part of the contribution's address.
 title: "IDiaSectionContrib::get_addressSection"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_addressSection
 
 Retrieves the section part of the contribution's address.
 
 ## Syntax
 
 ```C++
-HRESULT get_addressSection ( 
+HRESULT get_addressSection ( 
    DWORD* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-code.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-code.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section contains executable code."
+description: Retrieves a flag that indicates whether the section contains executable code.
 title: "IDiaSectionContrib::get_code"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_code
 
 Retrieves a flag that indicates whether the section contains executable code.
 
 ## Syntax
 
 ```C++
-HRESULT get_code ( 
+HRESULT get_code ( 
    BOOL* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-code16bit.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-code16bit.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section contains 16-bit code."
+description: Retrieves a flag that indicates whether the section contains 16-bit code.
 title: "IDiaSectionContrib::get_code16bit"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,6 +12,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_code16bit
 
 Retrieves a flag that indicates whether the section contains 16-bit code.

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-comdat.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-comdat.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section is a COMDAT record."
+description: Retrieves a flag that indicates whether the section is a COMDAT record.
 title: "IDiaSectionContrib::get_comdat"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_comdat
 
 Retrieves a flag that indicates whether the section is a COMDAT record.
 
 ## Syntax
 
 ```C++
-HRESULT get_comdat ( 
+HRESULT get_comdat ( 
    BOOL* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-compiland.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-compiland.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a reference to the compiland symbol that contributed this section."
+description: Retrieves a reference to the compiland symbol that contributed this section.
 title: "IDiaSectionContrib::get_compiland"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_compiland
 
 Retrieves a reference to the compiland symbol that contributed this section.
 
 ## Syntax
 
 ```C++
-HRESULT get_compiland ( 
+HRESULT get_compiland ( 
    IDiaSymbol** pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-compilandid.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-compilandid.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves the compiland identifier for the section."
+description: Retrieves the compiland identifier for the section.
 title: "IDiaSectionContrib::get_compilandId"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_compilandId
 
 Retrieves the compiland identifier for the section.
 
 ## Syntax
 
 ```C++
-HRESULT get_compilandId ( 
+HRESULT get_compilandId ( 
    DWORD* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-datacrc.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-datacrc.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves the cyclic redundancy check (CRC) of the data in the section."
+description: Retrieves the cyclic redundancy check (CRC) of the data in the section.
 title: "IDiaSectionContrib::get_dataCrc"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_dataCrc
 
 Retrieves the cyclic redundancy check (CRC) of the data in the section.
 
 ## Syntax
 
 ```C++
-HRESULT get_dataCrc ( 
+HRESULT get_dataCrc ( 
    DWORD* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-discardable.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-discardable.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section can be discarded."
+description: Retrieves a flag that indicates whether the section can be discarded.
 title: "IDiaSectionContrib::get_discardable"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_discardable
 
 Retrieves a flag that indicates whether the section can be discarded.
 
 ## Syntax
 
 ```C++
-HRESULT get_discardable ( 
+HRESULT get_discardable ( 
    BOOL* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-execute.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-execute.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section is executable as code."
+description: Retrieves a flag that indicates whether the section is executable as code.
 title: "IDiaSectionContrib::get_execute"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_execute
 
 Retrieves a flag that indicates whether the section is executable as code.
 
 ## Syntax
 
 ```C++
-HRESULT get_excute ( 
+HRESULT get_excute ( 
    BOOL* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-informational.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-informational.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag indicating whether a section contains comments or similar information."
+description: Retrieves a flag indicating whether a section contains comments or similar information.
 title: "IDiaSectionContrib::get_informational"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,6 +12,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_informational
 
 Retrieves a flag indicating whether a section contains comments or similar information.

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-initializeddata.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-initializeddata.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section contains initialized data."
+description: Retrieves a flag that indicates whether the section contains initialized data.
 title: "IDiaSectionContrib::get_initializedData"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_initializedData
 
 Retrieves a flag that indicates whether the section contains initialized data.
 
 ## Syntax
 
 ```C++
-HRESULT get_initializedData ( 
+HRESULT get_initializedData ( 
    BOOL* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-length.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-length.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves the number of bytes in a section."
+description: Retrieves the number of bytes in a section.
 title: "IDiaSectionContrib::get_length"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_length
 
 Retrieves the number of bytes in a section.
 
 ## Syntax
 
 ```C++
-HRESULT get_length ( 
+HRESULT get_length ( 
    DWORD* pRetVal
 );
 ```

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-nopad.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-nopad.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag indicating whether the section should not be padded to the next memory boundary."
+description: Retrieves a flag indicating whether the section should not be padded to the next memory boundary.
 title: "IDiaSectionContrib::get_nopad"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,6 +12,7 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_nopad
 
 Retrieves a flag indicating whether the section should not be padded to the next memory boundary.

diff --git a/docs/debugger/debug-interface-access/idiasectioncontrib-get-notcached.md b/docs/debugger/debug-interface-access/idiasectioncontrib-get-notcached.md
@@ -1,5 +1,5 @@
 ---
-description: "Retrieves a flag that indicates whether the section cannot be cached."
+description: Retrieves a flag that indicates whether the section cannot be cached.
 title: "IDiaSectionContrib::get_notCached"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -12,14 +12,15 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
+
 # IDiaSectionContrib::get_notCached
 
 Retrieves a flag that indicates whether the section cannot be cached.
 
 ## Syntax
 
 ```C++
-HRESULT get_notCached ( 
+HRESULT get_notCached ( 
    BOOL* pRetVal
 );
 ```