Seeding docs on nservicebus and masstransit interop

docs/.vitepress/config.js

@@ -115,6 +115,8 @@ export default {
                         {text: 'Endpoint Specific Operations', link: '/guide/messaging/endpoint-operations'},
                         {text: 'Broadcast to a Specific Topic', link: '/guide/messaging/broadcast-to-topic'},
                         {text: 'Message Expiration', link: '/guide/messaging/expiration'},
+                        {text: 'Interoperability with NServiceBus', link: '/guide/messaging/nservicebus'},
+                        {text: 'Interoperability with MassTransit', link: '/guide/messaging/masstransit'},
                     ]
                 },
                 {

docs/guide/messaging/masstransit.md

@@ -0,0 +1,13 @@
+# Interoperability with MassTransit
+
+Wolverine is the new kid on the block, and it's quite likely that many folks will already be using MassTransit for messaging.
+Fortunately, Wolverine has some ability to exchange messages with NServiceBus applications, so both tools can live and
+work together.
+
+At this point, the interoperability is only built and tested for the [Rabbit MQ transport](./transports/rabbitmq.md).
+
+Here's a sample:
+
+snippet: sample_MassTransit_interoperability
+
+MORE SOON!

docs/guide/messaging/nservicebus.md

@@ -0,0 +1,13 @@
+# Interoperability with NServiceBus
+
+Wolverine is the new kid on the block, and it's quite likely that many folks will already be using NServiceBus for messaging. 
+Fortunately, Wolverine has some ability to exchange messages with NServiceBus applications, so both tools can live and
+work together.
+
+At this point, the interoperability is only built and tested for the [Rabbit MQ transport](./transports/rabbitmq.md).
+
+Here's a sample:
+
+snippet: sample_NServiceBus_interoperability
+
+MORE SOON!