Improve clarity and consistency in Kedify HTTP autoscaling documentation

Author: madeline-underwood

content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/http-scaling.md

@@ -9,7 +9,7 @@ In this section, you’ll gain hands-on experience with Kedify HTTP autoscaling.
 
 You will scale a real HTTP app exposed through Kubernetes Ingress using [Kedify’s HTTP Scaler](https://docs.kedify.io/scalers/http-scaler/), and then move on to deploy a simple application, enable autoscaling with a scaled object, generate load, and observe the system scale out and back in (including scale-to-zero when idle). 
 
-For more information, see [Scaling Deployments, StatefulSets & Custom Resources](https://keda.sh/docs/latest/concepts/scaling-deployments/) at the KEDA website.  
+For more information, see [Scaling Deployments, StatefulSets & Custom Resources](https://keda.sh/docs/latest/concepts/scaling-deployments/) on the KEDA website.  
 
 ## How it works
 
@@ -48,8 +48,6 @@ If your ingress controller service uses a different name or namespace, update th
 
 Now you will deploy a simple HTTP server and expose it using an Ingress resource. The source code for this application is available on the [Kedify GitHub repository](https://github.com/kedify/examples/tree/main/samples/http-server).
 
-### Deploy the application
-
 Run the following command to deploy your application:
 
 ```bash
@@ -121,9 +119,12 @@ spec:
 EOF
 ```
 
-Notes:
-- `RESPONSE_DELAY` adds ~300 ms latency per request, making scaling effects easier to see.
-- The Ingress uses host `application.keda`. To access this app, you will use your Ingress controller’s IP with a `Host:` header (shown below).
+## Key settings explained
+
+The manifest includes a few key options that affect scaling behavior:
+
+- `RESPONSE_DELAY` is set in the Deployment manifest above and adds approximately 300 ms latency per request; this slower response time increases the number of concurrent requests, making scaling effects easier to observe.
+- The ingress uses the host `application.keda`. To access this app, use your Ingress controller’s IP with a `Host:` header.
 
 ## Verify the application is running
 
@@ -163,6 +164,7 @@ The application is now running. Next, you will enable autoscaling so that it can
 ```bash
 cat <<'EOF' | kubectl apply -f -
 apiVersion: keda.sh/v1alpha1
+
 kind: ScaledObject
 metadata:
   name: application

content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/install-ingress.md

@@ -6,10 +6,10 @@ layout: "learningpathall"
 
 ## Install an ingress controller for HTTP autoscaling on Kubernetes
 
-Before deploying HTTP applications with Kedify autoscaling, you need an ingress controller to handle incoming traffic. Most managed Kubernetes services (AWS EKS, Google GKE, Azure AKS) do not include an ingress controller by default. In this learning path, you install the NGINX Ingress Controller with Helm and target Arm64 nodes.
+Before deploying HTTP applications with Kedify autoscaling, you need an ingress controller to handle incoming traffic. Most managed Kubernetes services (AWS EKS, Google GKE, Azure AKS) do not include an ingress controller by default. In this Learning Path, you install the NGINX Ingress Controller with Helm and target Arm64 nodes.
 
 {{% notice Note %}}
-If your cluster already has an ingress controller installed and configured, you can skip this step and proceed to the [HTTP scaling guide](../http-scaling/).
+If your cluster already has an ingress controller installed and configured, you can skip this step and proceed to the [Autoscale HTTP applications with Kedify and Kubernetes Ingress section](../http-scaling/).
 {{% /notice %}}
 
 ## Install the NGINX Ingress Controller with Helm
@@ -51,11 +51,11 @@ If no value is printed, wait briefly and re-run the command.
 
 You have two options:
 
-- **Option 1 — DNS (recommended for production):**  
-  Create a DNS record pointing `application.keda` to the external IP address or hostname of your ingress controller.
+- Option 1: DNS (recommended for production):
+  create a DNS record pointing `application.keda` to the external IP address or hostname of your ingress controller.
 
-- **Option 2 — host header (quick test):**  
-  Use the external IP address or hostname directly with a `Host:` header:
+- Option 2: host header (quick test):  
+  use the external IP address or hostname directly with a `Host:` header:
   ```bash
   curl -H "Host: application.keda" http://$INGRESS_IP
   ```

content/learning-paths/servers-and-cloud-computing/kedify-http-autoscaling/install-kedify-helm.md

@@ -5,7 +5,7 @@ layout: "learningpathall"
 ---
 
 ## Overview
-In this section, you will install Kedify on your Kubernetes cluster using Helm. You will add the Kedify chart repository, install KEDA (Kedify build), the HTTP Scaler, and the Kedify Agent. You will then verify the installation. This enables HTTP autoscaling on Kubernetes with KEDA and Kedify, including arm64 nodes.
+In this section, you will install Kedify on your Kubernetes cluster using Helm. You will add the Kedify chart repository, then install three separate Helm charts: KEDA (Kedify build) for event-driven autoscaling, the HTTP Scaler for HTTP-based scaling, and the Kedify Agent for connecting your cluster to Kedify's cloud service. You will then verify the installation. This enables HTTP autoscaling on Kubernetes with KEDA and Kedify, including arm64 nodes.
 
 For more information and other installation methods on Arm, see the [Kedify installation documentation](https://docs.kedify.io/installation/helm#installation-on-arm).
 
@@ -28,7 +28,7 @@ kubectl get secret -n keda kedify-agent -o=jsonpath='{.data.apikey}' | base64 --
 Otherwise, in the Kedify dashboard go to **Organization** → **API Keys**, select **Create Agent Key**, and copy the key.
 
 {{% notice Note %}}
-The API key is shared across all Agent installations. If you regenerate it, update existing Agents and keep it secret.
+The API key is shared across all agent installations. If you regenerate it, update existing agents and keep it secret.
 {{% /notice %}}
 
 Optionally, export these values for reuse in the following commands:
@@ -127,4 +127,4 @@ keda-operator-metrics-apiserver-xxxxx            1/1     Running   0          1m
 kedify-agent-xxxxx                               1/1     Running   0          1m
 ```
 
-Proceed to the next section to install an Ingress controller, deploy a sample HTTP app, and test autoscaling.
+Proceed to the next section to install an ingress controller, deploy a sample HTTP app, and test autoscaling.