maverick/docbrown
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix broken doc links (#2945) [ci skip]

Browse source
This commit is contained in:
Conor Fischer 2019-05-24 11:31:18 -05:00 • committed by Mac Siri
parent 37fabd08b1
commit 2a57e43bcb
3 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/getting-started/pull-request.md
View file

@ -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.

2
docs/installation/readme.md
View file

@ -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

2
docs/tests/integration-tests.md
View file

@ -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`.