Refining wording

Author: muiriswoulfe

README.md

@@ -150,8 +150,8 @@ Instructions on using the action within Azure Pipelines can be found
 
 ## Git History
 
-Depending on the nature of your repo history, it may be necessary to fetch Git
-history during checkout. This can be done by updating the `actions/checkout`
+Depending on the nature of your repository history, it may be necessary to fetch
+Git history during checkout. This can be done by updating the `actions/checkout`
 step:
 
 ```YAML
@@ -160,10 +160,10 @@ step:
 ```
 
 In many cases, `fetch-depth` will not be required so it is recommended not to
-set this unless the task explicitly requests it. It may also be possible to set
-this to a value greater than 0 if you only require a partial history, but it can
-be difficult to determine a value that will work consistently, due to the nature
-of Git history.
+set this unless the action explicitly requests it. It may also be possible to
+set this to a value greater than 0 if you only require a partial history, but it
+can be difficult to determine a value that will work consistently, due to the
+nature of Git history.
 
 ## Troubleshooting
 

docs/azure-pipelines-task.md

@@ -96,8 +96,8 @@ name `PR_METRICS_ACCESS_TOKEN` cannot be altered.
 
 ## Git History
 
-Depending on the nature of your repo history, it may be necessary to fetch Git
-history during checkout. This can be done by updating the `checkout` step:
+Depending on the nature of your repository history, it may be necessary to fetch
+Git history during checkout. This can be done by updating the `checkout` step:
 
 ```YAML
 - checkout: self