Ensure compliance with the "Modularization" part of CQA 2 pre-migration requirements. This includes, but might not be limited to, the following issues:

• 3. Tuning Satellite Server with predefined profiles does not follow the procedure template: It's "introduction" is too large. We should look into splitting it into multiple modules, probably creating a whole assembly.
• 4. Migrating from internal Satellite databases to external databases does not follow the assembly template: The assembly introduction contains a command. The superfluous parts of the intro could be moved, for example simply to 4.1. PostgreSQL as an external database considerations.
• 19. Using webhooks does not follow the assembly template: Its introduction is too long. Find a way to split part of the introduction into a separate module.
• 7. Backing up Foreman server and Smart Proxy server: Another long assembly introduction whose parts should be split into a separate "overview" module.
• 12.2. Performing a full backup of Satellite Server or Capsule Server: This is currently a single procedure file but should be turned into an assembly and split into smaller chunks as modules.
• 13.3. Backup and restore Capsule Server by using a virtual machine snapshot: The assembly introduction is actually a short description + a procedure module becuase it is asking users to perform a procedure. Find a way to split it into a separate module. The result would likely be: 13. Backup and restore CS [...], 13.1 ,[procedure] 13.2 [procedure] 
• 10.10.1. Creating a granular permission filter by using Satellite web UI: The steps in this procedure are not short, actionable action items.