Refine documentation formatting (#3080)

* Fix installation command formatting in the readme.

* Add more syntax highlighting to JS test docs.

* Add syntax highlighting to transport docs.

README.md

@@ -48,7 +48,7 @@ npm install @aspnet/signalr --registry https://dotnet.myget.org/f/aspnetcore-dev
 We also have a MsgPack protocol library which is installed via:
 
 ```bash
- npm install @aspnet/signalr-protocol-msgpack
+npm install @aspnet/signalr-protocol-msgpack
 ```
 
 ## Deploying

docs/JSUnitTests.md

@@ -66,7 +66,7 @@ Just make sure you remove `.only` when you finish running that test!
 
 You can also use the `-t` parameter to jest. That parameter takes a substring pattern to match against all tests to see if they should run. To improve the speed of the run, you should pair this up with the argument that takes a file path to filter on. For example, given these tests
 
-```
+```typescript
 describe("AbortSignal", () => {
     describe("aborted", () => {
         it("is false on initialization", () => {

specs/TransportProtocols.md

@@ -22,7 +22,7 @@ The `POST [endpoint-base]/negotiate` request is used to establish a connection b
 
 1. A response that contains the `connectionId` which will be used to identify the connection on the server and the list of the transports supported by the server.
 
-  ```
+  ```json
   {
     "connectionId":"807809a5-31bf-470d-9e23-afaee35d8a0d",
     "availableTransports":[
@@ -50,7 +50,7 @@ The `POST [endpoint-base]/negotiate` request is used to establish a connection b
 
 2. A redirect response which tells the client which URL and optionally access token to use as a result.
 
-  ```
+  ```json
   {
     "url": "https://myapp.com/chat",
     "accessToken": "accessToken"
@@ -65,7 +65,7 @@ The `POST [endpoint-base]/negotiate` request is used to establish a connection b
 
 3. A response that contains an `error` which should stop the connection attempt.
 
-  ```
+  ```json
   {
     "error": "This connection is not allowed."
   }