Minor Text Changes

* Adding examples to G7 - If you register for a service, they track you, but that’s not this - props @MacManX
* Clarifying G10 - props Judith
* Make G15 less kludgy - props Judith
* Add mention in G17 that projects count too (if you’re not Chart.JS, don’t use their name)

guideline-07.md

@@ -1,10 +1,12 @@
 **7. The plugin may not “phone home” or track users without their informed, explicit, opt-in consent.**
 
-In the interest of protecting user privacy, plugins may not contact external servers without the explicit consent of the user. This is called ‘opt in.’  Documentation on how any user data is collected, and used, should be included in the plugin’s readme, preferably with a clearly stated privacy policy.
+In the interest of protecting user privacy, plugins may not contact external servers without the explicit consent of the user. This is called ‘opt in.’ Documentation on how any user data is collected, and used, should be included in the plugin’s readme, preferably with a clearly stated privacy policy.
 
 This restriction includes the following:
 
 * No unauthorized collection of user data. Users may be asked to submit information but it cannot be automatically recorded without  explicit confirmation from the user. 
 * Intentionally misleading users into submitting information as a requirement for use of the plugin itself is prohibited.
 * Images and scripts should be loaded locally as part of the plugin whenever possible. If external data (such as blocklists) is required, their inclusion must be made clear to the user.
-* Any third party advertisement mechanisms used within the plugin must  have all tracking features disabled by default. Advertisement mechanisms which do not have the capability of disabling user tracking features are prohibited.
+* Any third party advertisement mechanisms used within the plugin must  have all tracking features disabled by default. Advertisement mechanisms which do not have the capability of disabling user tracking features are prohibited.
+
+The sole exception to this policy is Software as a Service, such as Twitter, an Amazon CDN plugin, or Akismet. By installing, activating, registering, and configuring plugins that utilize those services, consent is granted.

guideline-10.md

@@ -1,3 +1,3 @@
 **10. The plugin must not embed external links or credits on the public site without explicitly asking the user’s permission.**
 
-All "Powered By" or credit displays and links included in the plugin code must be optional and default to _not_ show the links. Users must opt-in to displaying any and all credits and links. Plugins may not require credit or links in order to function. Services are permitted to brand their output as they see fit, provided the code is handled in the service and not the plugin.
+All "Powered By" or credit displays and links included in the plugin code must be optional and default to _not_ show on users' front-facing websites. Users must opt-in to displaying any and all credits and links. Plugins may not require credit or links be displayed in order to function. Services are permitted to brand their output as they see fit, provided the code is handled in the service and not the plugin.

guideline-15.md

@@ -1,5 +1,5 @@
-**15. All code changes to a plugin that has a Stable Tag of “trunk” must result in the version number being upgraded.**
+**15. All code changes to a plugin that has a Stable Tag of “trunk” must result in the version number being incrimented.**
 
-For the trunk and tags method, trunk can be continually updated without version number changes, while tags should generally not be updated past the initial tagging, unless the readme is being updated with regards to supporting the newest version of WordPress.
+If a developer is using tag folders for distribution of the latest version of their plugin, the trunk folder can be continually updated without version number changes. The tags folders should generally not be updated past the initial tagging, unless the readme is being updated with regards to supporting the newest version of WordPress.
 
-For more information on tagging, please read our [SVN directions on tagging](https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/#task-3) and [how the readme.txt works](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/) to better understand this. Remember: If you use tags and don’t increment versions, no one will get your updates.
+For more information on tagging, please read our [SVN directions on tagging](https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/#task-3) and [how the readme.txt works](https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/). Remember: If you use don’t increment versions of your plugins, no one will get your updates.

guideline-17.md

@@ -1,7 +1,7 @@
-**17. Respect trademarks.**
+**17. Respect trademarks and projects.**
 
-The use of trademarks as the sole or initial term of a plugin slug is prohibited unless proof of legal ownership/representation can be confirmed. For example, the [WordPress Foundation has trademarked the term “WordPress”](http://wordpressfoundation.org/trademark-policy/) and it is a violation to use “wordpress” in a domain name. This policy extends to plugin slugs. 
+The use of trademarks or other projects as the sole or initial term of a plugin slug is prohibited unless proof of legal ownership/representation can be confirmed. For example, the [WordPress Foundation has trademarked the term “WordPress”](http://wordpressfoundation.org/trademark-policy/) and it is a violation to use “wordpress” in a domain name. This policy extends to plugin slugs. 
 
-For example, only employees of Facebook should use the slug “Facebook,” or their brand in a context such as “Facebook Dancing Sloths.” Non-employees should use a format such as “Dancing Sloths for Facebook” instead to avoid potentially misleading users into believing the plugin was developed by Facebook. 
+As another example, only employees of Facebook should use the slug “Facebook,” or their brand in a context such as “Facebook Dancing Sloths.” Non-employees should use a format such as “Dancing Sloths for Facebook” instead to avoid potentially misleading users into believing the plugin was developed by Facebook. Similarly, if you don't represent the "Chart.js" project, it's inappropriate to use that as the name of your plugin.
 
-Original branding is recommended as it not only helps to avoid confusion, but is also often more memorable to the user.
+Original branding is recommended as it not only helps to avoid confusion, but is more memorable to the user.