6 files changed, 14 insertions, 14 deletions
diff --git a/doc/development/testing_guide/best_practices.md b/doc/development/testing_guide/best_practices.md
index 66bd56c13e8..613423dbd9a 100644
--- a/doc/development/testing_guide/best_practices.md
+++ b/doc/development/testing_guide/best_practices.md
@@ -1,4 +1,4 @@
-# Testing Best practices
+# Testing best practices
 
 ## Test speed
 
@@ -20,7 +20,7 @@ Here are some things to keep in mind regarding test performance:
 
 ## RSpec
 
-### General Guidelines
+### General guidelines
 
 - Use a single, top-level `describe ClassName` block.
 - Use `.method` to describe class methods and `#method` to describe instance
@@ -156,7 +156,7 @@ complexity of RSpec expectations.They should be placed under
 a certain type of specs only (e.g. features, requests etc.) but shouldn't be if
 they apply to multiple type of specs.
 
-#### have_gitlab_http_status
+#### `have_gitlab_http_status`
 
 Prefer `have_gitlab_http_status` over `have_http_status` because the former
 could also show the response body whenever the status mismatched. This would
diff --git a/doc/development/testing_guide/flaky_tests.md b/doc/development/testing_guide/flaky_tests.md
index d52fa9a662d..bbb2313ea7b 100644
--- a/doc/development/testing_guide/flaky_tests.md
+++ b/doc/development/testing_guide/flaky_tests.md
@@ -57,7 +57,7 @@ This was originally implemented in: https://gitlab.com/gitlab-org/gitlab-ce/merg
 - [Don't wait for AJAX when no AJAX request is fired](https://gitlab.com/gitlab-org/gitlab-ce/issues/30461): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10454
 - [Bis](https://gitlab.com/gitlab-org/gitlab-ce/issues/34647): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12626
 
-#### PhantomJS/WebKit related issues
+#### PhantomJS / WebKit related issues
 
 - Memory is through the roof! (TL;DR: Load images but block images requests!): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12003
 
diff --git a/doc/development/testing_guide/frontend_testing.md b/doc/development/testing_guide/frontend_testing.md
index 1f12ebddd50..0c63f51cb45 100644
--- a/doc/development/testing_guide/frontend_testing.md
+++ b/doc/development/testing_guide/frontend_testing.md
@@ -1,4 +1,4 @@
-# Frontend Testing
+# Frontend testing standards and style guidelines
 
 There are two types of test suites you'll encounter while developing frontend code
 at GitLab. We use Karma and Jasmine for JavaScript unit and integration testing,
@@ -62,7 +62,7 @@ describe('.methodName', () => {
   });
 });
 ```
-#### Testing Promises
+#### Testing promises
 
 When testing Promises you should always make sure that the test is asynchronous and rejections are handled.
 Your Promise chain should therefore end with a call of the `done` callback and `done.fail` in case an error occurred.
@@ -165,7 +165,7 @@ excluded tests (with `fdescribe` or `xdescribe`) to get karma to run only the
 tests you want while you're working on a specific feature, but make sure to
 remove these directives when you commit your code.
 
-## RSpec Feature Integration Tests
+## RSpec feature integration tests
 
 Information on setting up and running RSpec integration tests with
 [Capybara] can be found in the [Testing Best Practices](best_practices.md).
diff --git a/doc/development/testing_guide/index.md b/doc/development/testing_guide/index.md
index 9db664db066..38b1fe1a193 100644
--- a/doc/development/testing_guide/index.md
+++ b/doc/development/testing_guide/index.md
@@ -1,4 +1,4 @@
-# Testing Standards and Style Guidelines
+# Testing standards and style guidelines
 
 This document describes various guidelines and best practices for automated
 testing of the GitLab project.
@@ -31,14 +31,14 @@ changes should be tested.
 
 ---
 
-## [Testing Best practices](best_practices.md)
+## [Testing best practices](best_practices.md)
 
 Everything you should know about how to write good tests: RSpec, FactoryGirl,
 system tests, parameterized tests etc.
 
 ---
 
-## [Frontend Testing](frontend_testing.md)
+## [Frontend testing standards and style guidelines](frontend_testing.md)
 
 Everything you should know about how to write good Frontend tests: Karma,
 testing promises, stubbing etc.
@@ -59,7 +59,7 @@ parallelization, monitoring.
 
 ---
 
-## [Testing Rake Tasks](testing_rake_tasks.md)
+## [Testing Rake tasks](testing_rake_tasks.md)
 
 Everything you should know about how to test Rake tasks.
 
diff --git a/doc/development/testing_guide/testing_levels.md b/doc/development/testing_guide/testing_levels.md
index d6707f2ab75..9b9ba0baa71 100644
--- a/doc/development/testing_guide/testing_levels.md
+++ b/doc/development/testing_guide/testing_levels.md
@@ -67,7 +67,7 @@ run JavaScript tests, so you can either run unit tests (e.g. test a single
 JavaScript method), or integration tests (e.g. test a component that is composed
 of multiple components).
 
-## System tests or Feature tests
+## System tests or feature tests
 
 Formal definition: https://en.wikipedia.org/wiki/System_testing.
 
@@ -108,7 +108,7 @@ The reasons why we should follow these best practices are as follows:
 [Poltergeist]: https://github.com/teamcapybara/capybara#poltergeist
 [RackTest]: https://github.com/teamcapybara/capybara#racktest
 
-## Black-box tests or End-to-end tests
+## Black-box tests or end-to-end tests
 
 GitLab consists of [multiple pieces] such as [GitLab Shell], [GitLab Workhorse],
 [Gitaly], [GitLab Pages], [GitLab Runner], and GitLab Rails. All theses pieces
diff --git a/doc/development/testing_guide/testing_rake_tasks.md b/doc/development/testing_guide/testing_rake_tasks.md
index 8b135731e7f..5bf185dd7b5 100644
--- a/doc/development/testing_guide/testing_rake_tasks.md
+++ b/doc/development/testing_guide/testing_rake_tasks.md
@@ -1,4 +1,4 @@
-## Testing Rake Tasks
+## Testing Rake tasks
 
 To make testing Rake tasks a little easier, there is a helper that can be included
 in lieu of the standard Spec helper. Instead of `require 'spec_helper'`, use