Rhiannon Udall
--- a/CONTRIBUTING.md

+ 3

− 3
+++ b/CONTRIBUTING.md

+ 3

− 3
 # Contributing to bilby

-This is a short guide to contributing to bilby aimed at general LVC members who
+This is a short guide to contributing to bilby aimed at general LVK members who
 have some familiarity with python and git.  

 1. [Code of conduct](#code-of-conduct)
 @@ -19,7 +19,7 @@ have some familiarity with python and git.
 Everyone participating in the bilby community, and in particular in our issue
 tracker, merge requests, and chat channels, is expected to treat other people
 with respect and follow the guidelines articulated in the [Python Community
-Code of Conduct](https://www.python.org/psf/codeofconduct/).
+Code of Conduct](https://www.python.org/psf/codeofconduct/). Furthermore, members of the LVK collaboration must follow the [LVK Code of Conduct](https://dcc.ligo.org/LIGO-M1900037/public).

 ## Code style

 @@ -48,7 +48,7 @@ def my_new_function(x, y, print=False):
 ```
 3. Avoid inline comments unless necessary. Ideally, the code should make it obvious what is going on, if not the docstring, only in subtle cases use comments
 4. Name variables sensibly. Avoid using single-letter variables, it is better to name something `power_spectral_density_array` than `psda`.
-5. Don't repeat yourself. If code is repeated in multiple places, wrap it up into a function.
+5. Don't repeat yourself. If code is repeated in multiple places, wrap it up into a function. This also helps with the writing of robust unit tests (see below).


 ## Automated code checking
 @@ -155,7+155,7 @@
 Comments and questions may pertain to the functionality, but they may also
 relate to the code quality. We are keen to maintain a high standard of the
 code. This makes it easier to maintain, develop, and track down buggy
 behaviour. See the [Code style](#code-style) Section for an overview.

 **Reviewing Changes**