Revise quick start guide for standalone API Gateway

en/docs/api-gateway/quick-start-guide.md

@@ -1,6 +1,6 @@
 ---
 title: "API Platform Gateway Quick Start Guide"
-description: "Run API Platform Gateway with Docker Compose, deploy your first REST API configuration, and invoke it through the gateway in minutes."
+description: "Run API Platform Gateway in standalone mode with Docker Compose, deploy your first REST API, and invoke it through the gateway in minutes."
 canonical_url: https://wso2.com/api-platform/docs/api-gateway/quick-start-guide/
 md_url: https://wso2.com/api-platform/docs/api-gateway/quick-start-guide.md
 tags:
@@ -14,42 +14,69 @@ content_type: "quickstart"
 
 # Quick Start Guide
 
-### Using Docker Compose (Recommended)
+This guide walks you through running the API Platform Gateway in standalone mode using Docker Compose. Follow these steps to get your gateway running, deploy a REST API, and invoke it in minutes.
 
-### Prerequisites
+## Overview
 
-A Docker-compatible container runtime such as:
+The API Platform Gateway in standalone mode runs entirely in your own infrastructure without requiring a connection to any external control plane. All API configurations are managed directly through the gateway's built-in management API. This guide covers the fastest way to get started.
 
-- Docker Desktop (Windows / macOS)
-- Rancher Desktop (Windows / macOS)
-- Colima (macOS)
-- Docker Engine + Compose plugin (Linux)
+## Prerequisites
 
-Ensure `docker` and `docker compose` commands are available.
+Before you begin, ensure you have:
+
+- **wget** or **curl** installed
+- **unzip** installed
+- **Docker** installed and running
+- **Docker Compose** installed
+
+Verify that both `docker` and `docker compose` commands are available:
 
 ```bash
 docker --version
 docker compose version
 ```
 
-<!-- Replace `${version}` with the API Platform Gateway release version you want to run. -->
+## Setup Gateway
+
+### Step 1: Download the Gateway
+
+Run this command in your terminal to download and unzip the API Platform Gateway distribution:
 
 ```bash
-# Download distribution.
 wget https://github.com/wso2/api-platform/releases/download/gateway/v1.1.0/wso2apip-api-gateway-1.1.0.zip
-
-# Unzip the downloaded distribution.
 unzip wso2apip-api-gateway-1.1.0.zip
+```
 
+### Step 2: Start the Gateway
 
-# Start the complete stack
+Navigate to the extracted directory and start the complete gateway stack using Docker Compose:
+
+```bash
 cd wso2apip-api-gateway-1.1.0/
 docker compose up -d
+```
+
+### Step 3: Verify the Gateway
+
+Check that the gateway controller is up and healthy:
 
-# Verify gateway controller admin endpoint is running
+```bash
+# Check container status
+docker compose ps
+
+# Check gateway health
 curl http://localhost:9094/api/admin/v0.9/health
+```
+
+A successful response confirms the gateway is running and ready to accept API configurations.
+
+## Deploy an API
 
-# Deploy an API configuration
+### Step 1: Deploy an API Configuration
+
+Use the gateway's management API to deploy a sample Reading List REST API:
+
+```bash
 curl -X POST http://localhost:9090/api/management/v0.9/rest-apis \
   -u admin:admin \
   -H "Content-Type: application/yaml" \
@@ -89,25 +116,67 @@ spec:
     - method: DELETE
       path: /books/{id}
 EOF
+```
+
+### Step 2: Invoke the API
 
+Send a request to the deployed API through the gateway:
 
-# Test routing through the gateway
+**Over HTTP:**
+
+```bash
 curl -i http://localhost:8080/reading-list/v1.0/books
+```
+
+**Over HTTPS (with self-signed certificate):**
+
+```bash
 curl -ik https://localhost:8443/reading-list/v1.0/books
 ```
 
-### Stopping the Gateway
+A successful response returns a list of books from the upstream service, confirming that the gateway is routing traffic correctly.
 
-When stopping the gateway, you have two options:
+## Stopping the Gateway
+
+When you are done, you have two options for stopping the gateway:
+
+**Option 1: Stop and keep data (persisted APIs and configuration)**
 
-**Option 1: Stop runtime, keep data (persisted APIs and configuration)**
 ```bash
 docker compose down
 ```
-This stops the containers but preserves the `controller-data` volume. When you restart with `docker compose up`, all your API configurations will be restored.
 
-**Option 2: Complete shutdown with data cleanup (fresh start)**
+This stops the containers but preserves the `controller-data` volume. When you restart with `docker compose up`, all your deployed API configurations will be restored.
+
+**Option 2: Stop and remove all data (clean start)**
+
 ```bash
 docker compose down -v
 ```
-This stops containers and removes the `controller-data` volume. Next startup will be a clean slate with no persisted APIs or configuration.
+
+This stops the containers and removes the `controller-data` volume. The next startup will be a clean slate with no persisted APIs or configuration.
+
+## Next Steps
+
+Your standalone gateway is now running! Here's what to do next:
+
+- **Configure Policies**: Apply traffic management, security, and transformation [policies](policies/overview.md) to your APIs
+- **Connect to API Platform Cloud**: Run the gateway as a [Self-Hosted Gateway](../cloud/api-platform-gateway/getting-started.md) connected to the API Platform control plane for centralized management and analytics
+
+## Advanced Configuration
+
+For production environments or specific infrastructure requirements, see the detailed setup guides:
+
+- [Gateway Artifact Templating](setup/artifact-templating.md): Customize gateway artifacts using templates
+- [Configuring External Storage and Backends](setup/storage-and-backends.md): Set up external storage and backend connections
+- [Gateway Upstream Timeouts](setup/upstream-timeouts.md): Configure timeout settings for upstream services
+
+## Troubleshooting
+
+If the gateway does not start or the health check fails:
+
+1. **Check container status**: Run `docker compose ps` to see which containers are running
+2. **View logs**: Run `docker compose logs -f` to inspect gateway logs for errors
+3. **Verify ports**: Ensure ports `8080`, `8443`, `9090`, and `9094` are not already in use on your machine
+4. **Restart cleanly**: Run `docker compose down -v` and then `docker compose up -d` to start fresh
+