NPA-3901 Update Contributing Documentation

Author: JackPlowman

CONTRIBUTING.md

@@ -1,11 +1,15 @@
 # Contribution Guidelines
 
--   [Contribution Guidelines](#contribution-guidelines)
-    -   [Raising an Issue](#raising-an-issue)
-    -   [Contributing code](#contributing-code)
-        -   [Merge responsibility](#merge-responsibility)
-        -   [Branch naming](#branch-naming)
-        -   [Commit messages](#commit-messages)
+- [Contribution Guidelines](#contribution-guidelines)
+  - [Raising an Issue](#raising-an-issue)
+  - [Contributing code](#contributing-code)
+    - [Merge responsibility](#merge-responsibility)
+    - [Branch naming](#branch-naming)
+      - [Developers within the NHS](#developers-within-the-nhs)
+      - [Developers outside of the NHS](#developers-outside-of-the-nhs)
+    - [Commit messages](#commit-messages)
+      - [Developers within the NHS](#developers-within-the-nhs-1)
+      - [Developers outside of the NHS](#developers-outside-of-the-nhs-1)
 
 ## Raising an Issue
 
@@ -22,20 +26,44 @@ so please explain why the changes need to be made (unless it is self-evident).
 
 ### Merge responsibility
 
--   It is the responsibility of the reviewer to merge branches they have approved.
--   It is the responsibility of the author of the merge to ensure their merge is in a mergeable state.
--   It is the responsibility of the maintainers to ensure the merge process is unambiguous and automated where possible.
+- It is the responsibility of the reviewer to merge branches they have approved.
+- It is the responsibility of the author of the merge to ensure their merge is in a mergeable state.
+- It is the responsibility of the maintainers to ensure the merge process is unambiguous and automated where possible.
 
 ### Branch naming
 
+#### Developers within the NHS
+
 Branch names should be of the format:
 
-`apm-nnn-short-issue-description`
+`NPA-nnnn_short_issue_description`
+e.g. `NPA-1234_update_readme`
+
+Multiple branches are permitted for the same ticket.
+
+#### Developers outside of the NHS
+
+Branch names should be of the format:
+
+`short_issue_description`
 
 Multiple branches are permitted for the same ticket.
 
 ### Commit messages
 
+#### Developers within the NHS
+
+Commit messages should be formatted as follows:
+
+```
+APM-NNN Summary of changes
+
+Longer description of changes if explaining rationale is necessary,
+limited to 80 columns and spanning as many lines as you need.
+```
+
+#### Developers outside of the NHS
+
 Commit messages should be formatted as follows:
 
 ```

README.md

@@ -1,19 +1,19 @@
 # validated-relationships-service-api
 
-This is a RESTful FHIR API for the [Validated Relationship Service API](https://digital.nhs.uk/developer/api-catalogue/validated-relationship-service).
+This is a RESTful FHIR API for the [Validated Relationship Service](https://digital.nhs.uk/developer/api-catalogue/validated-relationship-service).
 
 Consumers of the API will find developer documentation on the [NHS Digital Developer Hub](https://digital.nhs.uk/developer/api-catalogue/validated-relationship-service).
 
 This repository does _not_ include the Validated Relationship Service FHIR API back-end. That is part of 'Proxy Validated Relationship Service' repository which is not currently open source.
 
 ## Table of Contents
 
--   [validated-relationships-service-api](#validated-relationships-service-api)
-    -   [Table of Contents](#table-of-contents)
-    -   [Repository Structure](#repository-structure)
-    -   [Contributing](#contributing)
-    -   [Development \& Testing](#development--testing)
-        -   [Licensing](#licensing)
+- [validated-relationships-service-api](#validated-relationships-service-api)
+  - [Table of Contents](#table-of-contents)
+  - [Repository Structure](#repository-structure)
+  - [Contributing](#contributing)
+  - [Development \& Testing](#development--testing)
+    - [Licensing](#licensing)
 
 ## Repository Structure
 
@@ -30,7 +30,7 @@ Contributions to this project are welcome from anyone, providing that they confo
 
 ## Development & Testing
 
-All development commands and documentation can be found in [DEVELOPMENT_GUIDE.md](./DEVELOPMENT_GUIDE.md).
+Development documentation can be found in [DEVELOPMENT_GUIDE.md](./DEVELOPMENT_GUIDE.md).
 
 ### Licensing