fixup! Tidy up commit

Author: franrob-projects

src/pages/docs/protocols/index.mdx

@@ -9,9 +9,9 @@ Ably SDKs are the recommended method for connecting to Ably because they offer s
 
 Protocol adapters offer an alternative method for connecting to Ably. The advantage to protocol adapters is that they require fewer resources in terms of memory and network overhead such as in smaller footprint devices, or on a platform where an Ably SDK isn't available such as an Arduino-based IoT wearable. The potential drawback to consider when evaluating protocol adapters is that they do not support the full set of Ably features, for example the MQTT protocol adapter does not support presence, and the SSE protocol adapter does not support automatic token renewal.
 
-## Migration support <a id="migration-support"/>
+## Migrate to Ably <a id="migration-support"/>
 
-Ably helps customers migrate from other data streaming networks including PubNub and Pusher. Protocol adapters facilitate risk-free migration by allowing you to use existing protocols and client libraries while transitioning to Ably client libraries over time.
+Ably helps customers migrate from other data streaming networks including PubNub and Pusher. Protocol adapters facilitate risk-free migration by allowing you to use existing protocols and client libraries while transitioning to Ably SDKs over time.
 
 Protocol adapters ensure interoperability between different protocols. For example, you can publish sensor data from an MQTT device, subscribe to that data using a Pusher client library for dashboard display, support mobile apps using Ably SDKs, and process data using AMQP worker queues - all within the same system.
 

src/pages/docs/protocols/pubnub.mdx

@@ -22,11 +22,10 @@ A typical migration from PubNub to Ably follows these steps:
 
 1. Change the host name for all of your PubNub client library integrations to use Ably's endpoints.
 
-2. Migrate one app at a time over to Ably client libraries. At this stage, some of your apps will be using PubNub client libraries and others will be using Ably's client libraries. Since the adapter translates the PubNub protocol, there's no interruption and interoperability between both protocols is maintained.
+2. Migrate one app at a time over to Ably SDKs. At this stage, some of your apps will be using PubNub client libraries and others will be using Ably's SDKs. Since the adapter translates the PubNub protocol, there's no interruption and interoperability between both protocols is maintained.
 
-3. Migrate all your apps and servers to use Ably client libraries and terminate your old contracts.
+3. Migrate all your apps and servers to use Ably SDKs and terminate your old contracts.
 
-If you're interested in migrating from PubNub using protocol adapters, [get in touch](https://ably.com/contact).
 
 ## Supported features <a id="features"/>