From 2a57e43bcba825096bb6d5e59d59e942815812ec Mon Sep 17 00:00:00 2001 From: Conor Fischer Date: Fri, 24 May 2019 11:31:18 -0500 Subject: [PATCH] Fix broken doc links (#2945) [ci skip] --- docs/getting-started/pull-request.md | 2 +- docs/installation/readme.md | 2 +- docs/tests/integration-tests.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/getting-started/pull-request.md b/docs/getting-started/pull-request.md index 9d3da767c..0ea69043c 100644 --- a/docs/getting-started/pull-request.md +++ b/docs/getting-started/pull-request.md @@ -5,7 +5,7 @@ title: Preparing a Pull Request # Preparing a pull request - Try to keep the pull requests small. A pull request should try its very best to address only a single concern. -- Make sure all tests pass and add additional tests for the code you submit. Checkout the [testing guide](/testing). +- Make sure all tests pass and add additional tests for the code you submit. Checkout the [testing guide](/tests). - Document your reasoning behind the changes. Explain why you wrote the code in the way you did. The code should be clear enough to explain what it does. - If there's an existing issue related to the pull request, reference to it by adding something like `References/Closes/Fixes/Resolves #305`, where 305 is the issue number. See [GitHub's own guide on closing issues via PR](https://github.com/blog/1506-closing-issues-via-pull-requests). - If you follow the pull request template, you can't go wrong. diff --git a/docs/installation/readme.md b/docs/installation/readme.md index 5e04eaf71..f9008d5cc 100644 --- a/docs/installation/readme.md +++ b/docs/installation/readme.md @@ -14,7 +14,7 @@ There are many different ways you can install the **development environment** so ## Installing locally -You can install DEV to your local machine and we have instructions for [Mac](/installation/mac-os), [Windows](/installation/windows) and [Linux](/installation/linux). +You can install DEV to your local machine and we have instructions for [Mac](/installation/mac), [Windows](/installation/windows) and [Linux](/installation/linux). ## Running Docker diff --git a/docs/tests/integration-tests.md b/docs/tests/integration-tests.md index 369f05f72..f015273f1 100644 --- a/docs/tests/integration-tests.md +++ b/docs/tests/integration-tests.md @@ -6,7 +6,7 @@ title: Integration Tests An integration test is when you need to test the interaction of multiple systems or parts of your application. -An integration test may seem similar to an [acceptance test](/tests/acceptance-tests.md). The main difference is that an acceptance test is from the perspective of the end user while an integration test is from the perspective of the developer. +An integration test may seem similar to an [acceptance test](/tests/acceptance-tests). The main difference is that an acceptance test is from the perspective of the end user while an integration test is from the perspective of the developer. Integration tests can be found in the directory `spec/requests`.