Update Gateway to remove a reference to NHibernate and replace it wit…

…h Sql

nservicebus/gateway/index.md

@@ -63,7 +63,7 @@ snippet: SendToSites
 In NServiceBus version 5 and above, the gateway is provided by the `NServiceBus.Gateway` NuGet package. In version 4 and below the gateway is part of the `NServiceBus` NuGet package.
 
 > [!NOTE]
-> The gateway requires NServiceBus persistence to operate though not all persisters support it. Currently, the gateway is supported only by InMemory, RavenDB and NHibernate persisters. If the configured persister doesn't support gateway, an exception will be thrown at endpoint startup.
+> The gateway requires NServiceBus persistence to operate though not all persisters support it. Currently, the gateway is supported only by InMemory, RavenDB and Sql persisters. If the configured persister doesn't support gateway, an exception will be thrown at endpoint startup.
 
 The gateway feature must be explicitly enabled using the configuration API:
 
@@ -83,4 +83,4 @@ However, a message sent by the NServiceBus 3.x Gateway will not be understood by
 
 ### Alternate channels
 
-[NServiceBus.Gateway.Channels.HttpVNext](https://github.com/welshdave/NServiceBus.Gateway.Channels.HttpVNext) is a [community package](/nservicebus/community/) that provides an HTTP channel implementation for the Gateway that doesn't use HTTP headers for message content or metadata. This makes it easier to use this channel in situations where HTTP headers may be modified, such as when a gateway is behind a reverse proxy such as NGINX.
+[NServiceBus.Gateway.Channels.HttpVNext](https://github.com/welshdave/NServiceBus.Gateway.Channels.HttpVNext) is a [community package](/nservicebus/community/) that provides an HTTP channel implementation for the Gateway that doesn't use HTTP headers for message content or metadata. This makes it easier to use this channel in situations where HTTP headers may be modified, such as when a gateway is behind a reverse proxy such as NGINX.