Docs: Distinguish examples in rules under Stylistic Issues part 6

[scriptdaemon]

Found some time to get a quick batch in.

object-curly-newline has the option to have separate configurations for object literals and destructuring assignments. My mind is drawing a blank, did we have any specific way to handle options for this kind of case?

@pedrottimark Mind giving this a look?

Slowly and surely... 😃

[mention-bot]

By analyzing the blame information on this pull request, we identified @mysticatea, @pedrottimark and @cjihrig to be potential reviewers

[eslintbot]

LGTM

[pedrottimark]

s/disallow/disallows/

[pedrottimark]

What do you think about deleting the comment in incorrect code below and adding it here?

This rule disallows trailing whitespace (spaces, tabs, and other Unicode whitespace characters) at the end of lines.

[pedrottimark]

Oh, sorry for making the second suggestion in an ambiguous way. We ended up with two similar sentences in the paragraph.

[pedrottimark]

@scriptdaemon Thank you. Nice work. 5 rules was a good amount for now.

In object-curly-newline

• I suggested some sentences. According to my notes, you will see more of this in the next few batches: one-var, padded-blocks, space-before-function-paren so we can learn as we go.
• Can you delete the hyphens in the list items under Options so they read like simple sentences
• Just to confirm the reasoning (which makes sense to me) you deleted the multiline and minProperties section because "multiline": true is the default option, [EDIT] therefore that example code is redundant with (and almost but not quite identical to) the example code in the preceding minProperties section?

[pedrottimark]

An alternative to consider for this heading is ObjectExpression and ObjectPattern

[eslintbot]

LGTM

[scriptdaemon]

@pedrottimark Thank you. Yeah, I figured 5 was better than none.

The examples for combined multiline and minProperties did seem redundant to me, so that is why I removed them.

[pedrottimark]

Only one more change in no-trailing-spaces where my line comment was ambiguous.

[eslintbot]

LGTM

[scriptdaemon]

@pedrottimark Fixed. Probably should have paid more attention when making the latest updates. 😄

[pedrottimark]

Looks good to me