Update routing_content_core_6.partial.md

transports/msmq/routing_content_core_6.partial.md

@@ -3,6 +3,9 @@ Mapping the logical destination to the physical address containing the queue and
 The preferred way of configuring the physical routing is via the instance mapping file.
 
 
+NOTE: When using instance mapping, the settings will have no effect on **audit/error** queue and **publish/subscribe** (except for subscription messages, subscription messages will be sent to all listed instances)
+
+
 ## Instance mapping file
 
 The instance mapping file is a simple XML file that has to be located either on a local hard drive or a network drive. When using MSMQ as the transport, NServiceBus will automatically look for an `instance-mapping.xml` file in `AppDomain.BaseDirectory`.

transports/msmq/routing_content_core_[,6).partial.md

@@ -1,5 +1,8 @@
+
+NOTE: When using instance mapping, the settings will have no effect on **audit/error** queue and **publish/subscribe** (except for subscription messages, subscription messages will be sent to all listed instances)
+
 Host name of the machine running each endpoint can be specified directly in the message-endpoint mapping configuration section by adding `@machine` suffix.
 
 snippet: endpoint-mapping-msmq
 
-When using MSMQ, if there is no `@machine` part, NServiceBus assumes the configured endpoint runs on a local machine.
+When using MSMQ, if there is no `@machine` part, NServiceBus assumes the configured endpoint runs on a local machine.

transports/msmq/routing_content_msmqtransport_[1,).partial.md

@@ -1,5 +1,9 @@
 Mapping the logical destination to the physical address containing the queue and host names is the responsibility of physical routing. 
 
+
+NOTE: When using instance mapping, the settings will have no effect on **audit/error** queue and **publish/subscribe** (except for subscription messages, subscription messages will be sent to all listed instances)
+
+
 The preferred way of configuring the physical routing is via the instance mapping file.