Merge pull request #2513 from zmbc/patch-1

Update CONTRIBUTING.md with correct link

CONTRIBUTING.md

@@ -46,7 +46,7 @@ In either case, we ask that you assign yourself to the relevant issue and open u
 
 You can always add further PRs to build extra functionality. Starting out with a minimum viable product and iterating makes for better software (in our opinion). It also helps get features out into the wild sooner.
 
-To get set up for development locally, see the [development quickstart](https://moj-analytical-services.github.io/splink/dev_guides/dev_guides/changing_splink/development_quickstart.html).
+To get set up for development locally, see the [development quickstart](https://moj-analytical-services.github.io/splink/dev_guides/changing_splink/development_quickstart.html).
 
 ## Best practices
 
@@ -71,4 +71,4 @@ If you have a larger feature, please consider creating a simple minimum-viable f
 1. Merge minimal feature, then create a new branch with additional features.
 2. Do not merge the initial feature branch, create additional feature branches from the reviewed branch.
 
-The best solution often depends on the specific feature being created and any other development work happening in that area of the codebase. If you are unsure, please ask the dev team for advice on how to best structure your changes in your initial PR and we can come to a decision together.
+The best solution often depends on the specific feature being created and any other development work happening in that area of the codebase. If you are unsure, please ask the dev team for advice on how to best structure your changes in your initial PR and we can come to a decision together.