From 86ba450bdb82374105cab7ec9d3263ffb5044976 Mon Sep 17 00:00:00 2001 From: Laurence de Bruxelles Date: Thu, 13 May 2021 14:52:18 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: EoinShaughnessy <72507742+EoinShaughnessy@users.noreply.github.com> --- CONTRIBUTING.md | 2 +- docs/documentation/setting-up-git.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 908dba40ec..2ec5c1fb41 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -47,4 +47,4 @@ branches. ### Commit hygiene -Please see our [Git style guide in the 'How to store source code' page of the GDS Way](https://gds-way.cloudapps.digital/standards/source-code.html#commit-messages) which describes how we prefer git history and commit messages to read. +Please see our [Git style guide in the 'How to store source code' page of the GDS Way](https://gds-way.cloudapps.digital/standards/source-code.html#commit-messages), which describes how we prefer Git history and commit messages to read. diff --git a/docs/documentation/setting-up-git.md b/docs/documentation/setting-up-git.md index ef5f45b0af..cccc30fc2e 100644 --- a/docs/documentation/setting-up-git.md +++ b/docs/documentation/setting-up-git.md @@ -80,7 +80,7 @@ git commit -m "First commit" ``` The message you put in the speech marks should be descriptive of the changes you are committing. This will help in the future if you or someone else needs to look back at your changes and know why you made them. -More information on writing good commit messages is in the [Git style guide in the 'How to store source code' page of the GDS Way](https://gds-way.cloudapps.digital/standards/source-code.html#commit-messages). +Read more about writing good commit messages in the [Git style guide in the 'How to store source code' page of the GDS Way](https://gds-way.cloudapps.digital/standards/source-code.html#commit-messages). ## 5) Check Git status again