Fixed formatting after preview check

Author: feversocial

docs/ca/devscu/manual-upgrade-alternatives/migration-sdk.md

@@ -1,11 +1,10 @@
 ---
 title: Migration SDK
 description: Learn how the open-source Migration SDK helps you plan and execute manual Spryker upgrades when the Spryker Code Upgrader cannot be used.
+keywords: Upgrade, MigrationSDK.
 template: howto-guide-template
 ---
 
-## Overview
-
 The **Migration SDK** is an open-source, community-developed tool that assists you in planning and executing manual upgrades of Spryker projects.  
 It analyzes your project and generates detailed reports, upgrade instructions, compatibility checks, and effort estimations.
 
@@ -14,11 +13,9 @@ Instead, it provides the data and guidance you need to perform updates manually
 
 {% info_block warningBox "Warning" %}
 The Migration SDK is a community-maintained tool. It is not officially supported or guaranteed by Spryker.  
-Use it at your own discretion. Contributions are welcome on [GitHub](https://github.com/spryker-projects/migration-program-sdk).
+Use it at your own discretion. Contributions are welcome on GitHub: https://github.com/spryker-projects/migration-program-sdk
 {% endinfo_block %}
 
----
-
 ## When to use the Migration SDK
 
 Use the Migration SDK when:
@@ -28,11 +25,9 @@ Use the Migration SDK when:
 - You need to perform a one-time manual upgrade to align your project with the latest Spryker version.
 
 {% info_block infoBox "Tip" %}
-After completing a manual upgrade using the Migration SDK, you can usually switch to the official **Spryker Code Upgrader** for future incremental updates.
+After completing a manual upgrade using the Migration SDK, you can usually switch to the official Spryker Code Upgrader for future incremental updates.
 {% endinfo_block %}
 
----
-
 ## Key capabilities
 
 The Migration SDK offers a collection of PHP console scripts that automate analysis and planning tasks for manual upgrades.  
@@ -54,8 +49,6 @@ The generated report helps you plan effort and identify risky or highly customiz
 Detect potential compatibility issues, such as outdated PHP versions, missing plugins, or missing glossary keys.  
 Use these reports to resolve incompatibilities before running updates.
 
----
-
 ## Typical workflow
 
 1. Clone the [Migration SDK repository](https://github.com/spryker-projects/migration-program-sdk).
@@ -66,19 +59,15 @@ Use these reports to resolve incompatibilities before running updates.
 
 All scripts and configuration options are documented in detail in the [GitHub README](https://github.com/spryker-projects/migration-program-sdk).
 
----
-
 ## Example use cases
 
 - **Project analysis:** Run the package analyzer to identify outdated modules before planning a major version upgrade.
 - **Upgrade planning:** Use the update instruction generator to divide your update process into manageable groups.
 - **Effort estimation:** Use the estimator report to predict development effort and prioritize modules.
 - **Compatibility validation:** Check for missing plugins or glossary entries to prevent regressions.
 
----
-
 ## Related documentation
 
-- [When and why to use manual upgrade](index.html)
-- [Spryker Code Upgrader](/docs/ca/devscu/spryker-code-upgrader/index.html)
+- [When and why to use manual upgrade](/docs/ca/devscu/spryker-code-upgrader/manual-upgrade-alternatives/when-and-why-to-do-manual-upgrade.html)
+- [Spryker Code Upgrader](/docs/ca/devscu/spryker-code-upgrader/spryker-code-upgrader.html)
 - [Upgradability Guidelines](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/upgradability-guidelines.html)

docs/ca/devscu/manual-upgrade-alternatives/when-and-why-to-do-manual-upgrade.md

@@ -4,13 +4,9 @@ description: Learn when to use manual upgrade instead of the Spryker Code Upgrad
 template: howto-guide-template
 ---
 
-## Overview
-
 The **Spryker Code Upgrader** is the primary and recommended tool for upgrading Spryker projects. It automates most upgrade steps, helping you keep your project aligned with the latest Spryker releases.  
 However, in some cases, you might need to perform a **manual upgrade**. This guide explains when that is necessary and introduces tools that can simplify the manual upgrade process.
 
----
-
 ## When to use a manual upgrade
 
 You might choose a manual upgrade in the following cases:
@@ -19,8 +15,6 @@ You might choose a manual upgrade in the following cases:
 - **Limited access** – You do not have entitlement or technical access to use the Spryker Code Upgrader.
 - **Custom upgrade strategy** – You prefer full control over upgrade steps or have a custom development workflow that does not align with automated upgrades.
 
----
-
 ## What to expect from manual upgrading
 
 Manual upgrades require you to analyze version differences, identify breaking changes, and apply updates directly in your codebase.  
@@ -35,7 +29,6 @@ This process can take more time and effort than using the Spryker Code Upgrader,
 Even when you perform a manual upgrade, follow the [Upgradability Guidelines](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/upgradability-guidelines.html) to keep your project compatible with future releases.
 
 {% endinfo_block %}
----
 
 ## How the Migration SDK can help
 
@@ -52,10 +45,9 @@ The Migration SDK does **not** modify your codebase or create merge requests. In
 The Migration SDK is not officially maintained or supported by Spryker. It is provided as a community project and used at your own discretion.  
 Contributions are welcome on [GitHub](https://github.com/spryker-projects/migration-program-sdk).
 {% endinfo_block %}
----
 
 ## Next steps
 
 - Learn more about the [Migration SDK](migration-sdk.html).
 - Read the [Upgradability Guidelines](/docs/dg/dev/guidelines/keeping-a-project-upgradable/upgradability-guidelines/upgradability-guidelines.html) to keep your project easier to upgrade in the future.
-- Review the [Spryker Code Upgrader](/docs/ca/devscu/spryker-code-upgrader/index.html) if your project meets the requirements for automated upgrades.
+- Review the [Spryker Code Upgrader](/docs/ca/devscu/spryker-code-upgrader.html) if your project meets the requirements for automated upgrades.