Merge pull request #16640 from alkohli/upd2

Fixed section title

Author: prmerger-automator[bot]

azure-local/update/solution-builder-extension.md

@@ -36,7 +36,7 @@ In addition to installing hardware updates, Solution Builder Extension may also
 | Advanced Solution Builder Extension Capability   |Description    |
 |---------------------------|---------------|
 | Health service integration | The Solution Builder Extension package can extend **Health Check** validation performed by Azure Local before various lifecycle actions (deployment, update, add node, repair node, and others) occur. The validation checks help to ensure issues are resolved before performing any specific lifecycle actions.<br/><br/> Hardware vendors typically use this integration to evaluate if there's a hardware issue that needs immediate attention. For example, it might identify problems with hardware vendor management software, a non-redundant power supply, or higher than expected temperatures. It could also identify SSD drive wear approaching a critical state. Be sure to review your hardware vendor's Solution Builder Extension documentation for details on hardware health checks supported by their extension. |
-| Solution builder extension download | The Solution Builder Extension package can implement **download connector** interfaces that allow Azure Local to download future SBE updates on behalf of the user. This feature enables new updates from your hardware vendor to show a **Ready** state instead of the [AdditionalContentRequired](solution-builder-extension.md#the-additionalcontentrequired-update-state) state mentioned later in this guide. Because these updates are ready to install without needing any files to be [imported](update-via-powershell-23h2.md#step-3-import-and--rediscover-updates) per an Azure Local instance, it makes it easy to install updates across multiple Azure Local instances simultaneously. <br><br> Hardware vendors often require customized SBE credentials for authentication to download their SBE extension files. Refer to your hardware vendor documentation for instructions on providing these credentials during [deployment on the Configuration](../deploy/deploy-via-portal.md#specify-the-deployment-settings) page or starting with Azure Local, version 2411, you can use the `Set-SolutionExtensionSecretLocation` cmdlet to update or add SBE credentials in Key Vault after deployment. |
+| Solution builder extension download | The Solution Builder Extension package can implement **download connector** interfaces that allow Azure Local to download future SBE updates on behalf of the user. This feature enables new updates from your hardware vendor to show a **Ready** state instead of the [AdditionalContentRequired](solution-builder-extension.md#the-additionalcontentrequired-update-state) state mentioned later in this guide. Because these updates are ready to install without needing any files to be [imported](update-via-powershell-23h2.md#step-3-import-and-rediscover-updates) per an Azure Local instance, it makes it easy to install updates across multiple Azure Local instances simultaneously. <br><br> Hardware vendors often require customized SBE credentials for authentication to download their SBE extension files. Refer to your hardware vendor documentation for instructions on providing these credentials during [deployment on the Configuration](../deploy/deploy-via-portal.md#specify-the-deployment-settings) page or starting with Azure Local, version 2411, you can use the `Set-SolutionExtensionSecretLocation` cmdlet to update or add SBE credentials in Key Vault after deployment. |
 | Customized deployment | The Solution Builder Extension package can implement customized steps that are executed automatically as part of the system deployment process. <br/><br/> Hardware vendors typically use this capability to configure or install any value-add software via their Solution Builder Extension for the solution.  |
 | Customized solution update | The Solution Builder Extension package can implement customized steps that are performed both before and after the main portion of the solution update process. Even when it isn't performing a Solution Builder Extension update, Solution Builder Extension packages that implement this capability always run these extra steps. For example, the execution of hardware vendor specific steps before or after Azure Stack HCI Operating System updates, when no updates to the Solution Builder Extension are needed. <br/><br/> Hardware vendors typically use this capability to prepare nodes for any update related tasks that may involve rebooting machines. |
 
@@ -206,5 +206,5 @@ For more information, see [Discover Solution Builder Extension updates](#discove
 
 ## Next steps
 
-- [Import and discover solution updates](../update/update-via-powershell-23h2.md#step-3-import-and--rediscover-updates).
+- [Import and discover solution updates](../update/update-via-powershell-23h2.md#step-3-import-and-rediscover-updates).
 - [Understand update phases of Azure Local, version 23H2](../update/update-phases-23h2.md).

azure-local/update/update-via-powershell-23h2.md

@@ -263,7 +263,7 @@ Follow these steps to discover the available updates for your system:
 
 You can now proceed to [Download and install the updates](#step-2-discover-the-updates).
 
-### Step 3: Import and  rediscover updates
+## Step 3: Import and rediscover updates
 
 Importing updates could be required in one of the following scenarios: