From d42d48349766d26f29997090083a231a8af6938c Mon Sep 17 00:00:00 2001 From: Ankush Goel Date: Mon, 25 Sep 2023 17:11:27 +0530 Subject: [PATCH] Update README.md --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 1e8a40303c0..eedf02a196c 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ Whether you’re running in the cloud, on bare metal, or using containers, you c The Gateway will be available on the following ports on localhost: `:8000` on which Kong listens for incoming HTTP traffic from your clients, and forwards it to your upstream services. -`:8001` on which the Admin API used to configure Kong listens. +`:8001` on which the Admin API is used to configure Kong listens. Next, follow the [quick start guide](https://docs.konghq.com/gateway-oss/latest/getting-started/configuring-a-service/ ) to tour the Gateway features. @@ -47,10 +47,10 @@ Next, follow the [quick start guide](https://docs.konghq.com/gateway-oss/latest/ By centralizing common API functionality across all your organization's services, the Kong API Gateway creates more freedom for engineering teams to focus on the challenges that matter most. The top Kong features include: -- Advanced routing, load balancing, health checking - all configurable via a RESTful admin API or declarative configuration. -- Authentication and authorization for APIs using methods like JWT, basic auth, OAuth, ACLs and more. +- Advanced routing, load balancing, and health checking - all configurable via a RESTful admin API or declarative configuration. +- Authentication and authorization for APIs using methods like JWT, basic auth, OAuth, ACLs, and more. - Proxy, SSL/TLS termination, and connectivity support for L4 or L7 traffic. -- Plugins for enforcing traffic controls, rate limiting, req/res transformations, logging, monitoring and including a plugin developer hub. +- Plugins for enforcing traffic controls, rate limiting, req/res transformations, logging, monitoring, and including a plugin developer hub. - Sophisticated deployment models like Declarative Databaseless Deployment and Hybrid Deployment (control plane/data plane separation) without any vendor lock-in. - Native [ingress controller](https://github.com/Kong/kubernetes-ingress-controller) support for serving Kubernetes.