Documentation updates

Formatting and link fixes

Author: lukebakken

README.md

@@ -1,9 +1,13 @@
-## RabbitMQ .NET Client [![Build status](https://ci.appveyor.com/api/projects/status/33srpo7owl1h3y4e?svg=true)](https://ci.appveyor.com/project/rabbitmq/rabbitmq-dotnet-client)
+## RabbitMQ .NET Client
+
+* AppVeyor: [![AppVeyor Build status](https://ci.appveyor.com/api/projects/status/33srpo7owl1h3y4e?svg=true)](https://ci.appveyor.com/project/rabbitmq/rabbitmq-dotnet-client)
+* TravisCI: [![Travis CI Build Status](https://travis-ci.org/rabbitmq/rabbitmq-dotnet-client.svg?branch=master)](https://travis-ci.org/rabbitmq/rabbitmq-dotnet-client)
 
 This repository contains source code of the [RabbitMQ .NET client](https://www.rabbitmq.com/dotnet.html).
 The client is maintained by the [RabbitMQ team at VMware](https://github.com/rabbitmq/).
 
-## Dependency (Binaries and Nuget Artifact)
+
+## Dependency (NuGet Artifact)
 
 ### Modern Versions
 
@@ -12,9 +16,7 @@ The client is [distributed via NuGet](https://www.nuget.org/packages/RabbitMQ.Cl
 ### Legacy Versions
 
 `3.6.x` and earlier releases were distributed [together with RabbitMQ server 3.6.x](https://github.com/rabbitmq/rabbitmq-server/releases/)
-as archives.
-
-[Release archive up to 3.4.3](https://bintray.com/rabbitmq/archive/rabbitmq-dotnet-client) is available from Bintray.
+as archives. You can also install `3.6.x` versions via [NuGet](https://www.nuget.org/packages/RabbitMQ.Client/).
 
 
 ## Tutorials and Documentation
@@ -37,18 +39,20 @@ For .NET Core users, 2.0 is the minimum supported version for `5.x` series.
 
 `3.6.x` releases support Linux and MacOS on [Mono](https://www.mono-project.com/).
 
+
 ## Change Log
 
-See [/CHANGELOG.md](https://github.com/rabbitmq/rabbitmq-dotnet-client/blob/master/CHANGELOG.md).
+See [CHANGELOG.md](CHANGELOG.md).
+
 
 ## Building from Source
 
-Please see [How to Run Tests](./RUNNING_TESTS.md) and [Building .NET Core](./BUILD_DOTNET_CORE.md)
-for build process overview.
+Please see [How to Run Tests](RUNNING_TESTS.md) for the build and test process overview.
+
 
 ## Contributing
 
-See [Contributing](./CONTRIBUTING.md) and [How to Run Tests](./RUNNING_TESTS.md).
+See [Contributing](CONTRIBUTING.md) and [How to Run Tests](RUNNING_TESTS.md).
 
 
 ## License

RUNNING_TESTS.md

@@ -1,13 +1,14 @@
 ## Overview
 
-.NET client's test suite assumes there's a RabbitMQ node listening on localhost:5672
+.NET client's test suite assumes there's a RabbitMQ node listening on `localhost:5672`
 (the default settings). SSL tests require a broker listening on the default
 SSL port. Connection recovery tests assume `rabbitmqctl` at `../rabbitmq-server/scripts/rabbitmqctl`
 can control the running node: this is the case when all repositories are cloned using
 the [umbrella repository](https://github.com/rabbitmq/rabbitmq-public-umbrella).
 
-It is possible to use [Visual Studio 2015 Community Edition](https://www.visualstudio.com/en-us/products/visual-studio-community-vs.aspx),
-.NET Core, and `dotnet.exe` in `PATH`, to build the client and run the test suite.
+It is possible to use Visual Studio Community Edition .NET Core, and
+`dotnet.exe` in `PATH`, to build the client and run the test suite.
+
 
 ## Building
 
@@ -27,39 +28,47 @@ This will complete the code AMQP 0-9-1 protocol code generation and build all pr
 
 ## Running Tests
 
-Tests can be run from Visual Studio using [NUnit Test Adapter](https://visualstudiogallery.msdn.microsoft.com/6ab922d0-21c0-4f06-ab5f-4ecd1fe7175d).
-Note that it may take some time for the adapter to discover tests in the assemblies.
+Tests can be run from Visual Studio using the NUnit Test Adapter.  Note that it
+may take some time for the adapter to discover tests in the assemblies.
 
-The test suite assumes there's a RabbitMQ node running locally with all defaults, and the tests will need to be able to run commands against the [rabbitmqctl](https://www.rabbitmq.com/rabbitmqctl.8.html) tool for that node. Two options to accomplish this are:
+The test suite assumes there's a RabbitMQ node running locally with all
+defaults, and the tests will need to be able to run commands against the
+[`rabbitmqctl`](https://www.rabbitmq.com/rabbitmqctl.8.html) tool for that node.
+Two options to accomplish this are:
 
 1. Team RabbitMQ uses [rabbitmq-public-umbrella](https://github.com/rabbitmq/rabbitmq-public-umbrella), which sets up a local RabbitMQ server [built from source](https://www.rabbitmq.com/build-server.html):
-```
+    ```
     git clone https://github.com/rabbitmq/rabbitmq-public-umbrella umbrella
     cd umbrella
     make co
     cd deps/rabbit
     make
     make run-broker
-```
+    ```
 
 2. You can load a RabbitMQ node in a [docker](https://www.docker.com/) container. You will need to create an environment variable `RABBITMQ_RABBITMQCTL_PATH` and set it to `DOCKER:<container_name>` (for example `DOCKER:rabbitmq01`). This tells the unit tests to run the `rabbitmqctl` commands through docker, in the format `docker exec rabbitmq01 rabbitmqctl <args>`:
-```
+    ```
     docker run -d --hostname rabbitmq01 --name rabbitmq01 -p 15672:15672 -p 5672:5672 rabbitmq:3-management
-```
+    ```
 
-Then, to run the tests on Windows use:
+    Then, to run the tests on Windows use:
 
+    ```
     run-test.bat
+    ```
 
-On MacOS, Linux, BSD use:
+    On MacOS, Linux, BSD use:
 
+    ```
     run-test.sh
+    ```
 
 Running individual tests and fixtures on Windows is trivial using the Visual Studio test runner.
 To run a specific tests fixture on MacOS or Linux, use the NUnit filter expressions to select the tests
 to be run:
 
-    dotnet test projects/Unit --filter "Name~TestAmqpUriParseFail"
-
+```
+dotnet test projects/Unit --filter "Name~TestAmqpUriParseFail"
 
-    dotnet test projects/Unit --filter "FullyQualifiedName~RabbitMQ.Client.Unit.TestHeartbeats"
+dotnet test projects/Unit --filter "FullyQualifiedName~RabbitMQ.Client.Unit.TestHeartbeats"
+```