Update README.md

Author: Chris Pearce

README.md

@@ -424,7 +424,7 @@ Test hooks are used for back-end tests e.g. testing some Ruby logic.
 
 Tracking hooks are used for tracking elements for analytics.
 
-They're simply classes namespaced like so: `.wf-test-` (test) / `.wf-track` (tracking) and follow the same naming convention as JS Hooks e.g. `.wf-test-[component]-[UI-it's-affecting]` / `.wf-track-[component]-[UI-it's-affecting]`.
+They're simply classes namespaced like so: `.test-` (test) / `.track` (tracking) and follow the same naming convention as JS Hooks e.g. `.test-[component]-[UI-it's-affecting]` / `.track-[component]-[UI-it's-affecting]`.
 
 **Test and Tracking hooks hooks do not use BEM.**
 
@@ -437,8 +437,8 @@ The order of the above hooks, within the `class` attribute, should be:
     2. Layout hook (`.l-`)
     3. Utility hook (`u-`)
 2. JS hooks (`.js-`)
-3. Test hooks (`.wf-test-`)
-4. Tracking hooks (`.wf-track-`)
+3. Test hooks (`.test-`)
+4. Tracking hooks (`.track-`)
 
 Example:
 
@@ -825,4 +825,4 @@ All of the above is about how we structure and form our CSS; they are very quant
 - [Our (CSS) Best Practices Are Killing US](http://www.stubbornella.org/content/2011/04/28/our-best-practices-are-killing-us/)
 - [Keep your CSS selectors short](http://csswizardry.com/2012/05/keep-your-css-selectors-short/)
 - [The single responsibility principle applied to CSS](http://csswizardry.com/2012/05/keep-your-css-selectors-short/)
-- [Principles for writing good CSS](http://blog.kaelig.fr/post/38377421139/principles-for-writing-good-css)
+- [Principles for writing good CSS](http://blog.kaelig.fr/post/38377421139/principles-for-writing-good-css)