Multi-line descriptions not correctly indented

[swissspidy]

Noticed this at https://github.com/wp-cli/entity-command/ where the <file> arg was documented like this:

	 * [<file>]
	 * : Read post content from <file>. If this value is present, the
	 *     `--post_content` argument will be ignored.
	 *
	 *   Passing `-` as the filename will cause post content to
	 *   be read from STDIN.

In the handbook this looks OK:

But in the readme generation the indentation is off:

That's because everything is indented with tabs, but this new paragraph is indented with spaces:

	[<file>]
		Read post content from <file>. If this value is present, the
		    `--post_content` argument will be ignored.

  Passing `-` as the filename will cause post content to
  be read from STDIN.

Or as a screenshot:

[swissspidy]

Still not working correctly, despite #282.

With something like this, the second paragraph is not indented at all:

	 * ## OPTIONS
	 *
	 * [--extra]
	 * : Show extended version information.
	 *
	 * Note: to retrieve the database revision for an individual subsite in a Multisite installation,
	 * use `wp option get db_version --url=<subsite>`.

And when I add a leading space to the second paragraph, it will have 1 more space in the readme than the first, so off by one:

	 * ## OPTIONS
	 *
	 * [--extra]
	 * : Show extended version information.
	 *
	 *  Note: to retrieve the database revision for an individual subsite in a Multisite installation,
	 *  use `wp option get db_version --url=<subsite>`.
	 *

And if I add two leading spaces, it looks nicely aligned in PHPDoc but it will be off by two in the readme:

	 * [--extra]
	 * : Show extended version information.
	 *
	 *   Note: to retrieve the database revision for an individual subsite in a Multisite installation,
	 *   use `wp option get db_version --url=<subsite>`.

I think all 3 options should get the same, correct alignment in the readme.

Of course don't wanna break ## EXAMPLES with its 4 spaces indention, so they should continue to work as is.

	 * ## EXAMPLES
	 *
	 *     # Update WordPress
	 *     $ wp core update
	 *     Updating to version 4.5.2 (en_US)...
	 *     Downloading update from https://downloads.wordpress.org/release/wordpress-4.5.2-no-content.zip...
	 *     Unpacking the update...
	 *     Cleaning up files...
	 *     No old files were removed.
	 *     Success: WordPress updated successfully.

Same for options:

	* [--format=<format>]
	 * : Render output in a particular format.
	 * ---
	 * options:
	 *   - table
	 *   - csv
	 *   - json
	 * ---