ADD TO: fix spelling

Author: jrfnl

wiki/Version-4.0-Developer-Upgrade-Guide.md

@@ -200,8 +200,8 @@ Typically, this may impact projects which call `new Config` consecutive times pr
 
 ##### Upgrading
 
-Typical work-arounds for the old behaviour will use `Reflection` to reset the `Config::$overriddenDefaults` property between instantiations.  
-These type of work-arounds can now be removed.
+Typical workarounds for the old behaviour will use `Reflection` to reset the `Config::$overriddenDefaults` property between instantiations.  
+These type of workarounds can now be removed.
 
 <p align="right"><a href="#table-of-contents">back to top</a></p>
 
@@ -338,7 +338,7 @@ This re-tokenization has now been removed.
 
 ##### Upgrading
 
-* Search your sniffs/code for `T_INSTANCEOF` and `'static'` to find any potential work-arounds in place for the old tokenization. Those can now be removed.
+* Search your sniffs/code for `T_INSTANCEOF` and `'static'` to find any potential workarounds in place for the old tokenization. Those can now be removed.
 
 <p align="right"><a href="#table-of-contents">back to top</a></p>
 
@@ -535,9 +535,9 @@ The Ruleset class now respects sniff selection via `--sniffs=...`, even when in
 
 **Upgrading**
 
-If your own test framework contained work-arounds to get round the previous restriction, it should now be safe to remove those work-arounds and to use the `--sniffs=...` argument when initiating the `Config` class.
+If your own test framework contained workarounds to get round the previous restriction, it should now be safe to remove those workarounds and to use the `--sniffs=...` argument when initiating the `Config` class.
 
-Typically, these type of work-around can be found by searching for calls to the `Ruleset::registerSniffs()` method.
+Typically, these type of workarounds can be found by searching for calls to the `Ruleset::registerSniffs()` method.
 
 <p align="right"><a href="#table-of-contents">back to top</a></p>