Last rewording amendments in cla thingy

Author: saxbophone

CONTRIBUTING.md

@@ -1,8 +1,8 @@
-# libsaxbospiral - Contributing
+# libsxbp - Contributing
 
-Thanks for considering contributing to libsaxbospiral!
+Thanks for considering contributing to libsxbp!
 
-To get started, [sign the Contributor License Agreement](https://www.clahub.com/agreements/saxbophone/libsaxbospiral).
+To get started, [sign the Contributor License Agreement](https://www.clahub.com/agreements/saxbophone/libsxbp).
 
 > [A copy of the CLA](CLA_INDIVIDUAL.md) is also available in this repository.
 
@@ -12,7 +12,7 @@ Here are some tips and general info about contributing to this project. Followin
 
 Before you contribute, check the work you're about to do fulfils one of these criteria:
 
-1. Implements a feature represented by an accepted issue in the project's [Github issue tracker](https://github.com/saxbophone/libsaxbospiral/issues)
+1. Implements a feature represented by an accepted issue in the project's [Github issue tracker](https://github.com/saxbophone/libsxbp/issues)
 2. Fixes a bug you discovered (preferably an issue should be created too, but for small or critical bugs, this may not be needed).
 
 Please also check that the work is not already being undertaken by someone else.
@@ -32,6 +32,6 @@ In addition, please make sure:
 
 ## Testing
 
-The unit tests for libsaxbospiral currently all reside in one C source file, `tests.c`. This isn't ideal, and I'm planning to clean these up at some point. Build and run the unit tests when you first pull down the code, rebuild and run them again when you've made your changes. Changes adding larger pieces of functionality will likely have additional tests requested for them, or an offer made to write the tests for them.
+The unit tests for libsxbp currently all reside in one C source file, `tests.c`. This isn't ideal, and I'm planning to clean these up at some point. Build and run the unit tests when you first pull down the code, rebuild and run them again when you've made your changes. Changes adding larger pieces of functionality will likely have additional tests requested for them, or an offer made to write the tests for them.
 
 Pull requests also go through [Travis CI](https://travis-ci.org/) for automated testing.