Update selecting-elements.md

[SoldierKB]

Formatted in paragraph for :checked selector

[arthurvr]

What your including isn't correct. We're in this case talking about elements, not about tags. Those shouldn't be wrapped within < and >. If you don't really understand the difference, I recommend to checkout http://perfectionkills.com/tag-is-not-an-element-or-is-it/.

This is a misconception made frequently.

[SoldierKB]

Ok, thanks for the link, it was interesting and I wasn't aware of it.
But have a look around this paragraph - above we have "any elements", as well as "any elements". So this type of brackets IS used here to denote HTML elements to avoid ambiguity. In the context we are talking about element to make distinction in the text it's HTML element, not just "select" word. And at the end we have "applies to or elements".
If we have it that way here - it should be that way, elsewhere the whole article should we rewritten. Isn't it ambiguous?

[arthurvr]

It's technically incorrect too, but let's not care about that. Everybody does it.

Best solution would in my opinion be to just wrap it between backticks. That would directly clarify that it's a technical term, not plain english. Overall technical stuff is wrapped between backticks in the site. Wanne PR?

tons, and `select` elements (for `select` elements 

[scottgonzalez]

We use "<select> elements" in jQuery content.

Note that this can only be discovered by browsing lots of existing content. This isn't currently covered in any of the various style guides right now. This needs to be covered in jquery/contribute.jquery.org#75.

[arthurvr]

This needs to be covered in jquery/contribute.jquery.org#75.

Ya surely. Ready to merge this one then. We'il discuss this in there later.

[SoldierKB]

So sorry, but I didn't really get it - should it be changed as I proposed or not? And later changed (fixed) every incorrect <...> to ...?

[arthurvr]

Nope, your PR was fine then. This should be included in the language style guide, but that's no reason to let this PR wait longer.

[SoldierKB]

Sorry again, I'm a little new to github and don't know/understand everything. Don't you mind me asking?
Who should approve my pull request? There are only several people who can do it, right? And we wait for one of this people to come, check PR and approve it in case everything is fine?
My previous PR is closed with unmerged commits, even though my changes are in master\on the page.
I just don't get how it works :).

[arthurvr]

Who should approve my pull request? There are only several people who can do it, right? And we wait for one of this people to come, check PR and approve it in case everything is fine?

Yes. Just to wait for somebody to merge this ;-)

My previous PR is closed with unmerged commits, even though my changes are in master\on the page.

It's merged, but with a little modifications then. Mostly that's just a little correction, or just the commit message which is changed.

[SoldierKB]

Thanks for explanation, I got it now. Thank you for you help and time, I really appreciate it!

[arthurvr]

By looking at the commit that closes your PR. For #401, that was 2510bdb.

For that PRs, the commits were just squashed together & the commit message changed.

Don't worry, when you start doing more, you'il learn it.