The build for this PR failed with the following error(s):

pages/common/exo-dbaas.md:
Error: Parse error on line 4:
...om/community/dbaas/>- List available D
-----------------------^
Expecting 'END_INFORMATION_LINK_URL', got 'NEWLINE'
pages/common/exo-dbaas.md:4: TLDR011 Page never contains more than a single empty line
pages/common/exo-iam.md:
Error: Parse error on line 4:
....com/community/iam/>- List all of the 
-----------------------^
Expecting 'END_INFORMATION_LINK_URL', got 'NEWLINE'
pages/common/exo-iam.md:4: TLDR011 Page never contains more than a single empty line
pages/common/exo-storage.md:
Error: Parse error on line 4:
.../community/storage/>- Create a new SOS
-----------------------^
Expecting 'END_INFORMATION_LINK_URL', got 'NEWLINE'
pages/common/exo-storage.md:4: TLDR011 Page never contains more than a single empty line

Please fix the error(s) and push again.

Not sure what you meant by alias pages.

Not sure what you meant by alias pages.

Found it a bit unclear for the naming convention when there are mass changes for a single command along with its sub commands.

In the templates, as I've understood, if its a sub command of a command its an alias page:

• For a new page addition: ls: add page, docker-container-rm: add alias page

Not sure what you meant by alias pages.

Found it a bit unclear for the naming convention when there are mass changes for a single command along with its sub commands.

In the templates, as I've understood, if its a sub command of a command its an alias page:

• For a new page addition: ls: add page, docker-container-rm: add alias page

An alias page is a page like this: https://github.com/tldr-pages/tldr/blob/main/pages/common/docker-container-rm.md?plain=1. It tells the user it should look to docker rm. For a subcommand (like docker rm) the title would be docker rm: add page. Hope this clarifies things

Correction: docker-rm: add page The title reflects the filename.

Please do not force push. It erases history and it's nice to see what changes were made after what comments.

Nice catch @MachiavelliII, we just did a Community revamp and this didn't cross my mind. Thanks!

If you notice anything to improve, just fire another pull request.