Merge pull request #2052 from rabbitmq/lukebakken/quote-formatting

Remove extra double quotes

Author: michaelklishin

tutorials/tutorial-five-dotnet.md

@@ -57,7 +57,7 @@ Messages sent to a `topic` exchange can't have an arbitrary
 `routing_key` - it must be a list of words, delimited by dots. The
 words can be anything, but usually they specify some features
 connected to the message. A few valid routing key examples:
-"`stock.usd.nyse`", "`nyse.vmw`", "`quick.orange.rabbit`". There can be as
+`stock.usd.nyse`, `nyse.vmw`, `quick.orange.rabbit`. There can be as
 many words in the routing key as you like, up to the limit of 255
 bytes.
 
@@ -78,49 +78,49 @@ In this example, we're going to send messages which all describe
 animals. The messages will be sent with a routing key that consists of
 three words (two dots). The first word in the routing key
 will describe speed, second a colour and third a species:
-"`<speed>.<colour>.<species>`".
+`<speed>.<colour>.<species>`.
 
-We created three bindings: Q1 is bound with binding key "`*.orange.*`"
-and Q2 with "`*.*.rabbit`" and "`lazy.#`".
+We created three bindings: Q1 is bound with binding key `*.orange.*`
+and Q2 with `*.*.rabbit` and `lazy.#`.
 
 These bindings can be summarised as:
 
   * Q1 is interested in all the orange animals.
   * Q2 wants to hear everything about rabbits, and everything about lazy
     animals.
 
-A message with a routing key set to "`quick.orange.rabbit`"
+A message with a routing key set to `quick.orange.rabbit`
 will be delivered to both queues. Message
-"`lazy.orange.elephant`" also will go to both of them. On the other hand
-"`quick.orange.fox`" will only go to the first queue, and
-"`lazy.brown.fox`" only to the second. "`lazy.pink.rabbit`" will
+`lazy.orange.elephant` also will go to both of them. On the other hand
+`quick.orange.fox` will only go to the first queue, and
+`lazy.brown.fox` only to the second. `lazy.pink.rabbit` will
 be delivered to the second queue only once, even though it matches two bindings.
-"`quick.brown.fox`" doesn't match any binding so it will be discarded.
+`quick.brown.fox` doesn't match any binding so it will be discarded.
 
 What happens if we break our contract and send a message with one or
-four words, like "`orange`" or "`quick.orange.new.rabbit`"? Well,
+four words, like `orange` or `quick.orange.new.rabbit`? Well,
 these messages won't match any bindings and will be lost.
 
-On the other hand "`lazy.orange.new.rabbit`", even though it has four
+On the other hand `lazy.orange.new.rabbit`, even though it has four
 words, will match the last binding and will be delivered to the second
 queue.
 
 > #### Topic exchange
 >
 > Topic exchange is powerful and can behave like other exchanges.
 >
-> When a queue is bound with "`#`" (hash) binding key - it will receive
+> When a queue is bound with `#` (hash) binding key - it will receive
 > all the messages, regardless of the routing key - like in `fanout` exchange.
 >
-> When special characters "`*`" (star) and "`#`" (hash) aren't used in bindings,
+> When special characters `*` (star) and `#` (hash) aren't used in bindings,
 > the topic exchange will behave just like a `direct` one.
 
 Putting it all together
 -----------------------
 
 We're going to use a `topic` exchange in our logging system. We'll
 start off with a working assumption that the routing keys of logs will
-have two words: "`<facility>.<severity>`".
+have two words: `<facility>.<severity>`.
 
 The code is almost the same as in the
 [previous tutorial](./tutorial-four-dotnet).
@@ -210,14 +210,14 @@ cd ReceiveLogsTopic
 dotnet run "#"
 ```
 
-To receive all logs from the facility "`kern`":
+To receive all logs from the facility `kern`:
 
 ```bash
 cd ReceiveLogsTopic
 dotnet run "kern.*"
 ```
 
-Or if you want to hear only about "`critical`" logs:
+Or if you want to hear only about `critical` logs:
 
 ```bash
 cd ReceiveLogsTopic
@@ -231,7 +231,7 @@ cd ReceiveLogsTopic
 dotnet run "kern.*" "*.critical"
 ```
 
-And to emit a log with a routing key "`kern.critical`" type:
+And to emit a log with a routing key `kern.critical` type:
 
 ```bash
 cd EmitLogTopic

tutorials/tutorial-five-elixir.md

@@ -57,7 +57,7 @@ Messages sent to a `topic` exchange can't have an arbitrary
 `routing_key` - it must be a list of words, delimited by dots. The
 words can be anything, but usually they specify some features
 connected to the message. A few valid routing key examples:
-"`stock.usd.nyse`", "`nyse.vmw`", "`quick.orange.rabbit`". There can be as
+`stock.usd.nyse`, `nyse.vmw`, `quick.orange.rabbit`. There can be as
 many words in the routing key as you like, up to the limit of 255
 bytes.
 
@@ -78,49 +78,49 @@ In this example, we're going to send messages which all describe
 animals. The messages will be sent with a routing key that consists of
 three words (two dots). The first word in the routing key
 will describe a celerity, second a colour and third a species:
-"`<celerity>.<colour>.<species>`".
+`<celerity>.<colour>.<species>`.
 
-We created three bindings: Q1 is bound with binding key "`*.orange.*`"
-and Q2 with "`*.*.rabbit`" and "`lazy.#`".
+We created three bindings: Q1 is bound with binding key `*.orange.*`
+and Q2 with `*.*.rabbit` and `lazy.#`.
 
 These bindings can be summarised as:
 
   * Q1 is interested in all the orange animals.
   * Q2 wants to hear everything about rabbits, and everything about lazy
     animals.
 
-A message with a routing key set to "`quick.orange.rabbit`"
+A message with a routing key set to `quick.orange.rabbit`
 will be delivered to both queues. Message
-"`lazy.orange.elephant`" also will go to both of them. On the other hand
-"`quick.orange.fox`" will only go to the first queue, and
-"`lazy.brown.fox`" only to the second. "`lazy.pink.rabbit`" will
+`lazy.orange.elephant` also will go to both of them. On the other hand
+`quick.orange.fox` will only go to the first queue, and
+`lazy.brown.fox` only to the second. `lazy.pink.rabbit` will
 be delivered to the second queue only once, even though it matches two bindings.
-"`quick.brown.fox`" doesn't match any binding so it will be discarded.
+`quick.brown.fox` doesn't match any binding so it will be discarded.
 
 What happens if we break our contract and send a message with one or
-four words, like "`orange`" or "`quick.orange.new.rabbit`"? Well,
+four words, like `orange` or `quick.orange.new.rabbit`? Well,
 these messages won't match any bindings and will be lost.
 
-On the other hand "`lazy.orange.new.rabbit`", even though it has four
+On the other hand `lazy.orange.new.rabbit`, even though it has four
 words, will match the last binding and will be delivered to the second
 queue.
 
 > #### Topic exchange
 >
 > Topic exchange is powerful and can behave like other exchanges.
 >
-> When a queue is bound with "`#`" (hash) binding key - it will receive
+> When a queue is bound with `#` (hash) binding key - it will receive
 > all the messages, regardless of the routing key - like in `fanout` exchange.
 >
-> When special characters "`*`" (star) and "`#`" (hash) aren't used in bindings,
+> When special characters `*` (star) and `#` (hash) aren't used in bindings,
 > the topic exchange will behave just like a `direct` one.
 
 Putting it all together
 -----------------------
 
 We're going to use a `topic` exchange in our logging system. We'll
 start off with a working assumption that the routing keys of logs will
-have two words: "`<facility>.<severity>`".
+have two words: `<facility>.<severity>`.
 
 The code is almost the same as in the
 [previous tutorial](./tutorial-four-elixir).
@@ -189,13 +189,13 @@ To receive all the logs run:
 mix run receive_logs_topic.exs "#"
 ```
 
-To receive all logs from the facility "`kern`":
+To receive all logs from the facility `kern`:
 
 ```bash
 mix run receive_logs_topic.exs "kern.*"
 ```
 
-Or if you want to hear only about "`critical`" logs:
+Or if you want to hear only about `critical` logs:
 
 ```bash
 mix run receive_logs_topic.exs "*.critical"
@@ -207,7 +207,7 @@ You can create multiple bindings:
 mix run receive_logs_topic.exs "kern.*" "*.critical"
 ```
 
-And to emit a log with a routing key "`kern.critical`" type:
+And to emit a log with a routing key `kern.critical` type:
 
 ```bash
 mix run emit_log_topic.exs "kern.critical" "A critical kernel error"

tutorials/tutorial-five-go.md

@@ -57,7 +57,7 @@ Messages sent to a `topic` exchange can't have an arbitrary
 `routing_key` - it must be a list of words, delimited by dots. The
 words can be anything, but usually they specify some features
 connected to the message. A few valid routing key examples:
-"`stock.usd.nyse`", "`nyse.vmw`", "`quick.orange.rabbit`". There can be as
+`stock.usd.nyse`, `nyse.vmw`, `quick.orange.rabbit`. There can be as
 many words in the routing key as you like, up to the limit of 255
 bytes.
 
@@ -78,49 +78,49 @@ In this example, we're going to send messages which all describe
 animals. The messages will be sent with a routing key that consists of
 three words (two dots). The first word in the routing key
 will describe speed, second a colour and third a species:
-"`<speed>.<colour>.<species>`".
+`<speed>.<colour>.<species>`.
 
-We created three bindings: Q1 is bound with binding key "`*.orange.*`"
-and Q2 with "`*.*.rabbit`" and "`lazy.#`".
+We created three bindings: Q1 is bound with binding key `*.orange.*`
+and Q2 with `*.*.rabbit` and `lazy.#`.
 
 These bindings can be summarised as:
 
   * Q1 is interested in all the orange animals.
   * Q2 wants to hear everything about rabbits, and everything about lazy
     animals.
 
-A message with a routing key set to "`quick.orange.rabbit`"
+A message with a routing key set to `quick.orange.rabbit`
 will be delivered to both queues. Message
-"`lazy.orange.elephant`" also will go to both of them. On the other hand
-"`quick.orange.fox`" will only go to the first queue, and
-"`lazy.brown.fox`" only to the second. "`lazy.pink.rabbit`" will
+`lazy.orange.elephant` also will go to both of them. On the other hand
+`quick.orange.fox` will only go to the first queue, and
+`lazy.brown.fox` only to the second. `lazy.pink.rabbit` will
 be delivered to the second queue only once, even though it matches two bindings.
-"`quick.brown.fox`" doesn't match any binding so it will be discarded.
+`quick.brown.fox` doesn't match any binding so it will be discarded.
 
 What happens if we break our contract and send a message with one or
-four words, like "`orange`" or "`quick.orange.new.rabbit`"? Well,
+four words, like `orange` or `quick.orange.new.rabbit`? Well,
 these messages won't match any bindings and will be lost.
 
-On the other hand "`lazy.orange.new.rabbit`", even though it has four
+On the other hand `lazy.orange.new.rabbit`, even though it has four
 words, will match the last binding and will be delivered to the second
 queue.
 
 > #### Topic exchange
 >
 > Topic exchange is powerful and can behave like other exchanges.
 >
-> When a queue is bound with "`#`" (hash) binding key - it will receive
+> When a queue is bound with `#` (hash) binding key - it will receive
 > all the messages, regardless of the routing key - like in `fanout` exchange.
 >
-> When special characters "`*`" (star) and "`#`" (hash) aren't used in bindings,
+> When special characters `*` (star) and `#` (hash) aren't used in bindings,
 > the topic exchange will behave just like a `direct` one.
 
 Putting it all together
 -----------------------
 
 We're going to use a `topic` exchange in our logging system. We'll
 start off with a working assumption that the routing keys of logs will
-have two words: "`<facility>.<severity>`".
+have two words: `<facility>.<severity>`.
 
 The code is almost the same as in the
 [previous tutorial](./tutorial-four-go).
@@ -299,13 +299,13 @@ To receive all the logs:
 go run receive_logs_topic.go "#"
 ```
 
-To receive all logs from the facility "`kern`":
+To receive all logs from the facility `kern`:
 
 ```bash
 go run receive_logs_topic.go "kern.*"
 ```
 
-Or if you want to hear only about "`critical`" logs:
+Or if you want to hear only about `critical` logs:
 
 ```bash
 go run receive_logs_topic.go "*.critical"
@@ -317,7 +317,7 @@ You can create multiple bindings:
 go run receive_logs_topic.go "kern.*" "*.critical"
 ```
 
-And to emit a log with a routing key "`kern.critical`" type:
+And to emit a log with a routing key `kern.critical` type:
 
 ```bash
 go run emit_log_topic.go "kern.critical" "A critical kernel error"

tutorials/tutorial-five-java.md

@@ -57,7 +57,7 @@ Messages sent to a `topic` exchange can't have an arbitrary
 `routing_key` - it must be a list of words, delimited by dots. The
 words can be anything, but usually they specify some features
 connected to the message. A few valid routing key examples:
-"`stock.usd.nyse`", "`nyse.vmw`", "`quick.orange.rabbit`". There can be as
+`stock.usd.nyse`, `nyse.vmw`, `quick.orange.rabbit`. There can be as
 many words in the routing key as you like, up to the limit of 255
 bytes.
 
@@ -78,49 +78,49 @@ In this example, we're going to send messages which all describe
 animals. The messages will be sent with a routing key that consists of
 three words (two dots). The first word in the routing key
 will describe speed, second a colour and third a species:
-"`<speed>.<colour>.<species>`".
+`<speed>.<colour>.<species>`.
 
-We created three bindings: Q1 is bound with binding key "`*.orange.*`"
-and Q2 with "`*.*.rabbit`" and "`lazy.#`".
+We created three bindings: Q1 is bound with binding key `*.orange.*`
+and Q2 with `*.*.rabbit` and `lazy.#`.
 
 These bindings can be summarised as:
 
   * Q1 is interested in all the orange animals.
   * Q2 wants to hear everything about rabbits, and everything about lazy
     animals.
 
-A message with a routing key set to "`quick.orange.rabbit`"
+A message with a routing key set to `quick.orange.rabbit`
 will be delivered to both queues. Message
-"`lazy.orange.elephant`" also will go to both of them. On the other hand
-"`quick.orange.fox`" will only go to the first queue, and
-"`lazy.brown.fox`" only to the second. "`lazy.pink.rabbit`" will
+`lazy.orange.elephant` also will go to both of them. On the other hand
+`quick.orange.fox` will only go to the first queue, and
+`lazy.brown.fox` only to the second. `lazy.pink.rabbit` will
 be delivered to the second queue only once, even though it matches two bindings.
-"`quick.brown.fox`" doesn't match any binding so it will be discarded.
+`quick.brown.fox` doesn't match any binding so it will be discarded.
 
 What happens if we break our contract and send a message with one or
-four words, like "`orange`" or "`quick.orange.new.rabbit`"? Well,
+four words, like `orange` or `quick.orange.new.rabbit`? Well,
 these messages won't match any bindings and will be lost.
 
-On the other hand "`lazy.orange.new.rabbit`", even though it has four
+On the other hand `lazy.orange.new.rabbit`, even though it has four
 words, will match the last binding and will be delivered to the second
 queue.
 
 > #### Topic exchange
 >
 > Topic exchange is powerful and can behave like other exchanges.
 >
-> When a queue is bound with "`#`" (hash) binding key - it will receive
+> When a queue is bound with `#` (hash) binding key - it will receive
 > all the messages, regardless of the routing key - like in `fanout` exchange.
 >
-> When special characters, "`*`" (star) and "`#`" (hash), aren't used in bindings,
+> When special characters, `*` (star) and `#` (hash), aren't used in bindings,
 > the topic exchange will behave just like a `direct` one.
 
 Putting it all together
 -----------------------
 
 We're going to use a `topic` exchange in our logging system. We'll
 start off with a working assumption that the routing keys of logs will
-have two words: "`<facility>.<severity>`".
+have two words: `<facility>.<severity>`.
 
 The code is almost the same as in the
 [previous tutorial](./tutorial-four-java).
@@ -212,13 +212,13 @@ To receive all the logs:
 java -cp $CP ReceiveLogsTopic "#"
 ```
 
-To receive all logs from the facility "`kern`":
+To receive all logs from the facility `kern`:
 
 ```bash
 java -cp $CP ReceiveLogsTopic "kern.*"
 ```
 
-Or if you want to hear only about "`critical`" logs:
+Or if you want to hear only about `critical` logs:
 
 ```bash
 java -cp $CP ReceiveLogsTopic "*.critical"
@@ -230,7 +230,7 @@ You can create multiple bindings:
 java -cp $CP ReceiveLogsTopic "kern.*" "*.critical"
 ```
 
-And to emit a log with a routing key "`kern.critical`" type:
+And to emit a log with a routing key `kern.critical` type:
 
 ```bash
 java -cp $CP EmitLogTopic "kern.critical" "A critical kernel error"