message: docs: markdown lint fixes
diff: @@ -15,14 +15,14 @@ If you are interested in contributing, please take a look at the [CONTRIBUTING](
  # Related Docs and Repositories
  -- @forcedotcom/cli-packages - Base Salesforce CLI command
  -- @forcedotcom/sfdx-plugin-generate - The generator plug-in for building plug-ins for Salesforce CLI
  +- @forcedotcom/cli-packages - Contains the base Salesforce CLI command, `SfdxCommand`.
  +- @forcedotcom/sfdx-plugin-generate - The generator plug-in for building plug-ins for Salesforce CLI.
  # Using TestSetup
  The Salesforce DX Core Library provides a unit testing utility to help with mocking and sand-boxing core components. This feature allows unit tests to execute without needing to make API calls to salesforce.com.
  -### Mocking AuthInfo
  +## Mocking AuthInfo
  Here you can mock authorization for a Salesforce scratch org.
  @@ -79,11 +79,11 @@ describe('Mocking a force server call', () => {
  });
  ```
  -### Using the Built-in Sinon Sandboxes
  +## Using the Built-in Sinon Sandboxes
  sfdx-core uses Sinon as its underlying mocking system. If you're unfamiliar with Sinon and it's sandboxing concept you can find more information here:
  https://sinonjs.org/
  -Sinon stubs and spys must be cleaned up after test invocations. To ease the use of Sinon with sfdx core we've exposed our sandbox in TestSetup. After adding your own stubs and/or spys they will automatically be cleaned up after each test using mocha's afterEach method.
  +Sinon `stub`s and `spy`s must be cleaned up after test invocations. To ease the use of Sinon with sfdx core we've exposed our sandbox in TestSetup. After adding your own `stub`s and/or `spy`s they will automatically be cleaned up after each test using mocha's afterEach method.
  ```typescript
  import { strictEqual } from 'assert';
  @@ -102,9 +102,9 @@ describe('Using the built in Sinon sandbox.', () => {
  });
  ```
  -### Testing Expected Failures
  +## Testing Expected Failures
  -It's important to have negative tests that ensure proper error handling. With _shouldThrow_ it's easy to test for expected async rejections.
  +It's important to have negative tests that ensure proper error handling. With `shouldThrow` it's easy to test for expected async rejections.
  ```typescript
  import { SfdxError } from '@salesforce/core';
  @@ -128,7 +128,7 @@ describe('Testing for expected errors', () => {
  });
  ```
  -### Testing Log Lines
  +## Testing Log Lines
  It's also useful to check expected values and content from log lines. TestSetup configures the sfdx-core logger to use an in memory LogLine storage structure. These can be easily accessed from tests.
  