contributing.markdown in brightbox-cli-0.17.0

- old
+ new

@@ -84,10 +84,10 @@
 * The real version should make a request, probably by a method defined on the real class in the service you defined earlier.
 * Each request should either return an Excon::Response (with a parsed body where appropriate) or raise an error.
 
 ## Tests
 
-Now would be a good time to write some tests to make sure what you have written works (and will continue to). I've tried a couple variations on testing in the past, but have settled on consolidated lifetime testing. These vary enough that its hard to give a single simple example, but you can see many examples in "tests/compute/requests/aws":https://github.com/geemus/fog/tree/master/tests/compute/requests/aws/.
+Now would be a good time to write some tests to make sure what you have written works (and will continue to). I've tried a couple variations on testing in the past, but have settled on consolidated lifetime testing. These vary enough that its hard to give a single simple example, but you can see many examples in "tests/compute/requests/aws":https://github.com/fog/fog/tree/master/tests/compute/requests/aws/.
 
 ### Highlights:
 * Reuse the same objects and take them through their whole life cycle (this is much faster, and most of the time if one portion fails the others would anyway).
 * Test the format of the output to ensure parsers match expectations (check the provider's api docs) and that mocks return matching data.
 * Test common failure cases and their behavior, you'll need to know how the service acts in these cases to make better mocks.