For example, the following issues have been observed:

• Parts of the API guide do not use assemblies. The guide should use assembly files to define groups of modules and their nesting, rather than for example `leveloffset=+2` and similar. Expected result: The guide does not contain `leveloffset=+2` or any other numerical value other than 1.
• 4.1. Calling the API in curl contains sections 4.1.3. Creating a user and 4.1.4. Modifying a user. These would fit better in the cheat sheet part of the guide, under an assembly named "Working with users". This is to ensure consistency with "Working with hosts" and "Working with lifecycle environments".
• 5.3. Uploading Content to Satellite Server is included as a "container" module but works as a procedure. An assembly is needed to replace 5.3, after which 5.3. Uploading Content to Satellite Server can be turned into a 5.3.1 procedure.