stuff

app/_data/docs_nav_konnect.yml

@@ -50,6 +50,12 @@
         url: /gateway-manager/dedicated-cloud-gateways/transit-gateways
       - text: Azure VNET Peering
         url: /gateway-manager/dedicated-cloud-gateways/azure-peering
+    - text: Serverless Gateways
+      items: 
+        - text: Overview
+          url: /gateway-manager/serverless-gateways/
+        - text: Provision a serverless Gateway
+          url: /gateway-manager/serverless-gateways/provision-serverless-gateway/
     - text: Data Plane Nodes
       items:
         - text: Installation Options

app/konnect/gateway-manager/serverless-gateways/index.md

@@ -1,45 +1,38 @@
 ---
 title: Serverless Gateways
-content_type: concept
 ---
 
 Serverless Gateways are lightweight data plane nodes that are fully managed by Kong in {{site.konnect_short_name}}.
-
-You don't need to host any data planes, while easily being able to deploy Kong gateways for your learning, prototyping, and hobbyist requirements.
 
 Serverless Gateways offer the following benefits:
 
-* {{site.konnect_short_name}} handles gateway provisioning and placement for you
-* very rapid spin-up time (sub 30s)
-* core subset of Kong gateway plugins
-* custom domains (coming soon)
-
-You can manage your Serverless Gateway nodes in [Gateway Manager](https://cloud.konghq.com/gateway-manager/).
-
-<img src="/assets/images/products/konnect/gateway-manager/konnect-control-plane-serverless-gateway-overview.png" alt="serverless gateway overview" style="max-width: 800px;">
-> _**Figure 1:** The Serverless Gateway wizard in the {{site.konnect_short_name}} UI._
+* {{site.konnect_short_name}} manages provisioning and placement.
+* Sub-30 second deployment time.
+* Access to {{site.base_gateway}} plugins.
 
+You can manage your Serverless Gateway nodes within [Gateway Manager](https://cloud.konghq.com/gateway-manager/).
 
 ## How do Serverless Gateways work? {#serverless-features}
 
 {% include_cached /md/konnect/deployment-topologies.md %}
 
-> _**Figure 2:** Data planes are hosted in the cloud by Kong. The control plane connects to the database, and the data planes receive configuration from the control plane. The number and size of data plane nodes is abstracted away by Kong, and you only have to worry about running your application._
+> _**Figure 2:** Data planes are hosted in the cloud by Kong. The control plane connects to the database, and the data planes receive a configuration from the control plane._
 
-When you create a Serverless Gateway, {{site.konnect_short_name}} creates a control plane. This control plane, like other {{site.konnect_short_name}} control planes, is hosted by {{site.konnect_short_name}}. {{site.konnect_short_name}} then provisions a hosted data plane for you and automatically configures the connection to the control plane, before providing the user with an auto-generated, easy-to-use hostname in the form `https://kong-xxxxxx.kongcloud.dev`.
+When you create a Serverless Gateway, {{site.konnect_short_name}} creates a control plane. This control plane, like other {{site.konnect_short_name}} control planes, is hosted by {{site.konnect_short_name}}. {{site.konnect_short_name}} then provisions a hosted data plane for you and automatically configures the connection to the control plane, before providing the user with an auto-generated, unique hostname in the form of `https://kong-xxxxxx.kongcloud.dev`.
 
-Serverless Gateways are designed to be fast to provision and lightweight from a maintenance and overhead point-of-view. Therefore is it not possible to configure:
+Serverless Gateways are designed to be fast to provision and lightweight, therefore it is not possible to configure:
 
-* Kong version (this is defaulted to the latest version and periodically automatically upgraded)
-* The number of data planes that are deployed
-* The size of the data planes that are deployed
-* The region that the data planes are deployed to (this usually aligns with your Konnect CP region but is not guaranteed)
+* {{site.base_gateway}} version. The default is `latest` and is automatically upgraded.
+* The number of data planes.
+* The size of the data planes.
+* The region that the data planes are deployed to. Typically the data planes are deployed on the same region as the {{site.konnect_short_name}} control plane, but with Serverless Gateways this is not guaranteed.
 
-Control planes in {{site.konnect_short_name}} **cannot** contain both Serverless Gateway and self-managed data plane nodes.
+{:.note}
+>**Note**: Control planes in {{site.konnect_short_name}} **cannot** contain both Serverless Gateway and self-managed data plane nodes.
 
 ## Networking
 
-Serverless Gateways only support public networking. There are currently no capabilities for private networking between your data centers and hosted Kong data planes. For use cases where private networking is required, [Dedicated Cloud Gateways](/konnect/gateway-manager/dedicated-cloud-gateways) with [AWS Transit Gateways](/konnect/gateway-manager/dedicated-cloud-gateways/transit-gateways/) may be a better choice.
+Serverless Gateways only supports public networking. There are currently no capabilities for private networking between your data centers and hosted Kong data planes. For use cases where private networking is required, [Dedicated Cloud Gateways](/konnect/gateway-manager/dedicated-cloud-gateways) with [AWS Transit Gateways](/konnect/gateway-manager/dedicated-cloud-gateways/transit-gateways/) may be a better choice.
 
 ## Plugin considerations for Serverless Gateways
 There are some limitations for plugins with Serverless Gateways:

app/konnect/gateway-manager/serverless-gateways/provision-serverless-gateway.md

@@ -15,9 +15,9 @@ This guide explains how to provision a [Serverless Gateway](/konnect/gateway-man
 {% navtab UI %}
 1. From [Gateway Manager](https://cloud.konghq.com/gateway-manager), click the **New Gateway** button and select **Serverless**.
 
-1. Enter a name (and optional description and / or labels) for your serverless gateway and click **Create**.
+1. Enter a name, optionally a description or label, for your serverless gateway and click **Create**.
 
-Your serverless gateway is now provisioned with data plane attached. You can use it like you would any other {{site.base_gateway}} in {{site.konnect_short_name}}.
+Your serverless gateway is now provisioned with the data plane attached. You can use it like you would any other {{site.base_gateway}} in {{site.konnect_short_name}}.
 
 The URL where your serverless gateway can be accessed is shown in the top `Overview` section of the Control Plane page.
 <img src="/assets/images/products/konnect/gateway-manager/konnect-control-plane-serverless-gateway-proxy.png" alt="serverless gateway proxy url" style="max-width: 600px;">
@@ -89,35 +89,8 @@ The {{site.konnect_short_name}} API uses [Personal Access Token (PAT)](/konnect/
 	* `control_plane_geo`: The geo of the control plane.
 	* `region`: The region you want to deploy the data plane in.
 
-    You should get a `201` response like the following:
-
-    ```json
-	{
-		"kind": "serverless.v0",
-		"id": "1ed33954-dd7f-40b5-8bd3-b2d91e4be99a",
-		"control_plane_id": "23be21c0-5984-4698-aa1f-ac258d77f0d1",
-		"control_plane_geo": "us",
-		"dataplane_group_config": [
-			{
-				"region": "na"
-			}
-		],
-		"dataplane_groups": [
-			{
-				"id": "e3d7bc7d-c0ff-4bdb-972a-9193d5c64d07",
-				"region": "na",
-				"state": "initializing",
-				"created_at": "2024-10-15T21:25:29.924Z",
-				"updated_at": "2024-10-15T21:25:29.924Z"
-			}
-		],
-		"created_at": "2024-10-15T21:25:29.924Z",
-		"updated_at": "2024-10-15T21:25:29.924Z",
-		"entity_version": 1
-	}
-    ```
+    You should get a `201` response which means your serverless gateway is now provisoned. You can use it like you would any other {{site.base_gateway}} in {{site.konnect_short_name}}.
 
-Your serverless gateway is now provisioned. You can use it like you would any other {{site.base_gateway}} in {{site.konnect_short_name}}.
 {% endnavtab %}
 {% endnavtabs %}