resolve reviewer comments

Author: Orin-Thomas

learn-pr/advocates/configure-manage-website-application/includes/1-website-application-virtual-directory.md

@@ -4,9 +4,9 @@ IIS organizes web content through a hierarchy of sites, applications, and virtua
 
 IIS structures web content in a three-tier hierarchy:
 
-1. **Website (Site).** The top-level container. Each site has at least one binding (IP address, port, and optional host name) that identifies incoming requests. A site maps to a physical root directory on disk.
-1. **Web Application.** A child container within a site. Applications have their own application pool assignment and can have separate configuration settings from the parent site. Use applications when you need isolated configuration, a different .NET runtime, or a dedicated worker process identity for a portion of a site.
-1. **Virtual Directory.** A pointer from a URL path to a physical directory on disk (which may be on a different volume or UNC path). Virtual directories don't have their own application pool and inherit the parent application's settings.
+- **Website (Site).** The top-level container. Each site has at least one binding (IP address, port, and optional host name) that identifies incoming requests. A site maps to a physical root directory on disk.
+- **Web Application.** A child container within a site. Applications have their own application pool assignment and can have separate configuration settings from the parent site. Use applications when you need isolated configuration, a different .NET runtime, or a dedicated worker process identity for a portion of a site.
+- **Virtual Directory.** A pointer from a URL path to a physical directory on disk (which may be on a different volume or UNC path). Virtual directories don't have their own application pool and inherit the parent application's settings.
 
 > [!NOTE]
 > This hierarchy is stored in the central IIS configuration file, ApplicationHost.config, located at %windir%\system32\inetsrv\config\.
@@ -37,7 +37,7 @@ To add a new site in IIS manager:
    - Port: Enter 80 (or another port if 80 is already in use and you're hosting multiple sites on the same IP address but differentiating based on port).
    - Host name: Enter the FQDN for this site, for example www.contoso.com. Host names are required when multiple sites share port 80 or 443 on the same IP address. The sites are differentiated by IIS using the HTTP host header value in each incoming request.
 
-   ![Screenshot showing the Add Website dialog box](../media/add-website.png)
+   ![Screenshot showing the Add Website dialog box.](../media/add-website.png)
 
 1. Leave Start Website immediately checked unless you want to configure the site before it begins serving requests.
 1. Select OK.
@@ -86,7 +86,7 @@ Granting permissions directly to that identity ensures:
 - Other application pools on the same server can't read or execute the content
 - You avoid using broad identities like Everyone, Users, or IIS_IUSRS
 
-Granting `Read and Execute` adheres to the principle of least privilege as IIS only needs read access to serve static content and load assemblies, and execute is require for binaries such as ASP.NET and native modules. You shouldn't assign the Write privilege as this will limit attacks such as:
+Granting `Read and Execute` adheres to the principle of least privilege as IIS only needs read access to serve static content and load assemblies, and execute is required for binaries such as ASP.NET and native modules. You shouldn't assign the Write privilege as this will limit attacks such as:
 
 - Web shell uploads
 - Defacement attacks
@@ -96,15 +96,15 @@ Granting `Read and Execute` adheres to the principle of least privilege as IIS o
 
 To add a Web Application within a Site
 
-1. In the Connections pane, expand Sites, then select on the Contoso site.
+1. In the Connections pane, expand Sites, then select the Contoso site.
 1. Right-click the site and select Add Application.
 1. In the Add Application dialog, configure:
    - Alias: The URL path segment, for example demoapp (accessible at www.contoso.com/demoapp).
    - Application pool: Select or create a dedicated pool.
    - Physical path: Enter the path to the application's files, for example d:\demoapp.
 1. Select OK.
 
-![Screenshot showing the Add Application dialog box](../media/add-application.png)
+![Screenshot showing the Add Application dialog box.](../media/add-application.png)
 
 You can accomplish this with the following PowerShell command:
 
@@ -125,7 +125,7 @@ To add a virtual directory within a site using IIS Manager, perform the followin
    - Physical path: Enter the directory path, for example D:\shared\downloads.
 1. Select OK.
 
-To add a virtual directory using PowerShell, perform the following steps:
+You can add a virtual directory using the PowerShell `New-WebVirtualDirectory` cmdlet. For example, to add a new virtual directory named `downloads` to the `Contoso` site, run the command:
 
 ```powershell
 New-WebVirtualDirectory -Site "Contoso" `

learn-pr/advocates/configure-manage-website-application/includes/2-application-pool-worker-process.md

@@ -21,7 +21,7 @@ To create an application pool using IIS Manager, perform the following steps:
    - Managed pipeline mode: Select Integrated.
 1. Select OK.
 
-![Screenshot of the Add Application Pool dialog box](../media/application-pool.png)
+![Screenshot of the Add Application Pool dialog box.](../media/application-pool.png)
 
 To edit an existing pool, double-click it or select it and select Basic Settings in the Actions pane.
 
@@ -50,7 +50,7 @@ To configure application pool recycling in IIS Manager, perform the following st
    - Memory-based recycling: Set virtual memory and private memory limits (in KB) to trigger recycling if the worker process exceeds those thresholds.
 1. Select Next to configure recycling event log settings, then select Finish.
 
-![Screenshot of the Recycling Conditions dialog box](../media/recycle-condition.png)
+![Screenshot of the Recycling Conditions dialog box.](../media/recycle-condition.png)
 
 You use the `Set-ItemProperty` cmdlet to configure application pool recycling using PowerShell. For example, to configure a regular interval, run the following command:
 

learn-pr/advocates/configure-manage-website-application/includes/3-binding-host-header.md

@@ -36,7 +36,7 @@ To add and edit site bindings in IIS Manager, perform the following steps:
 
 To edit an existing binding: select it in the list and select Edit. To remove a binding: select it and select Remove. Removing the only binding makes the site inaccessible.
 
-You managing bindings in PowerShell with the `WebBinding` cmdlets. For example:
+You manage bindings in PowerShell with the `WebBinding` cmdlets. For example:
 
 ```powershell
 # Add an HTTP binding with a host header
@@ -75,7 +75,7 @@ To enable SNI in IIS Manager:
 > [!NOTE]
 > Every HTTPS site sharing the same IP and port 443 must have SNI enabled. If even one site on that IP/port doesn't use SNI, it conflicts with the others.
 
-To enabling SNI with PowerShell, use the `WebBinding` cmdlets. For example:
+To enable SNI with PowerShell, use the `WebBinding` cmdlets. For example:
 
 ```powershell
 # SslFlags: 0 = no SNI, 1 = SNI, 2 = central certificate store

learn-pr/advocates/configure-manage-website-application/includes/4-advanced-site-configuration.md

@@ -1,6 +1,6 @@
 Beyond basic site creation and bindings, IIS provides a rich set of per-site and per-application configuration options that affect how content is served and how errors are handled. In this unit, you configure custom HTTP error pages, implement URL redirection, manage MIME types, enable HTTP compression, and configure request filtering to block unwanted or potentially harmful traffic.
 
-## Custom Error Pages
+## Custom error pages
 
 By default, IIS returns a generic HTTP error page when a client encounters a `4xx` or `5xx` status code. Customizing error pages improves the user experience and prevents accidental disclosure of internal diagnostic details.
 
@@ -31,7 +31,7 @@ Set-WebConfiguration `
   }
 ```
 
-## MIME Types
+## MIME types
 
 MIME types tell clients (browsers) how to interpret the content being served. If a file extension isn't registered in IIS, IIS returns a `404.3` error instead of serving the file, even if the file exists on disk.
 
@@ -57,7 +57,7 @@ Add-WebConfigurationProperty -PSPath "IIS:\Sites\Contoso" `
     -Value @{ fileExtension = ".avif"; mimeType = "image/avif" }
 ```
 
-## HTTP Compression
+## HTTP compression
 
 HTTP compression reduces response size, improving page load times and reducing bandwidth consumption. IIS supports two compression types:
 
@@ -89,7 +89,7 @@ Set-WebConfigurationProperty `
     -PSPath "IIS:\" -Name "doDynamicCompression" -Value $true
 ```
 
-## Request Filtering
+## Request filtering
 
 Request filtering is a built-in IIS security module that inspects incoming requests and blocks those that match defined rules. It's installed by default and runs early in the request pipeline, before most application code executes.
 
@@ -137,7 +137,7 @@ Add-WebConfigurationProperty -PSPath $sitePath `
 > [!NOTE]
 > Overly aggressive request filtering can cause legitimate requests to fail. Test filtering rules in a staging environment before deploying to production. Review IIS logs for `404.x` and `400` errors that may indicate blocked legitimate traffic.
 
-## Using the Built-In HTTP Redirect Feature
+## Using the built-In HTTP redirect feature
 
 For simple whole-site redirects, IIS includes a built-in HTTP Redirect feature that doesn't require the URL Rewrite module: