style-guide: add grouping documentation

[Managor]

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The page(s) follow the style guide.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known):

[Managor]

I'm asking for feedback if this should be documented.

[gutjuri]

I agree that it makes sense to document this

[gutjuri]

Suggested change

	For example `adb disconnect` has a single way using it, but `adb` is expansive enough that it doesn't fit in the main page. Normally `adb disconnect` is used in combination with `adb pair` and `adb connect`, thus it makes sense to group these together into a single page. For example:
	For example `adb disconnect` has a single way using it, but `adb` is expansive enough that it doesn't fit in the main page. Normally, `adb disconnect` is used in combination with `adb pair` and `adb connect`, thus it makes sense to group these together into a single page. For example:

[gutjuri]

Suggested change

	Sometimes commands and subcommands are single use but are meant to be used in combination with other commands. In these cases it makes sense to move them on the same page.
	Sometimes commands are meant to be used in combination with other commands. In these cases it makes sense to move them on the same page.