Don't use yoursite.com as a multisite site name placeholder in example.settings.local.php

Agreed with the issue summary -- the Drupal project also has a standard that we should use example.com (as you say, to be in line with the rest of the Internet).

I don't quite agree with the patch though:

 * To activate this feature, copy and rename it such that its path plus
- * filename is 'sites/yoursite.com/settings.local.php'. Then, go to the bottom
- * of 'sites/yoursite.com/settings.php' and uncomment the commented lines that
+ * filename is 'sites/*/settings.local.php'. Then, go to the bottom
+ * of 'sites/*/settings.php' and uncomment the commented lines that
  * mention 'settings.local.php'.

I think maybe it should say something like "... path plus filename is 'sites/SITEDIR/settings.local.php', where SITEDIR is your site's directory..." -- would that be clearer? I just don't think putting a * in an instruction is very clear, without explaining what to substitute for the *.

Also, the */ in there is ending the comment! That is why it is getting "invalid PHP syntax". Oops!

RE #5, look at sites.php, which I think is where the multi-site setup is documented, or maybe it's a readme in the sites top-level folder. We should definitely make sure that the terminology is consistent between all of them. Because this file could be going in sites/default or sites/example.com or sites/2048:example.com, or whatever... and actually I think in 8 the possibilities are even greater, due to the necessity of having a sites.php? Seems like we had a docs issue about that a month or two ago. Anyway... that is where I would start looking.

After reading your suggestions, I decided to change "yoursite.com" to "example.com" and added a line of explanation that "example.com is, in fact, your site name.

That looks great to me, thanks!

However, there is an extra space at the end of one of the lines. If you plan to work on Drupal patches (and I hope you will!), you may want to set your editor to either highlight or strip out end-of-line spaces. Most programming editors have a setting for that.

Thanks! I just made the fix and resubmitted the patch.

Thanks, looks good!

Thanks again! Committed to 8.0.x.