Update total scalers in catalog (#1549)

* Update total scalers in catalog

Signed-off-by: rickbrouwer <[email protected]>

* Improve sentence

Signed-off-by: rickbrouwer <[email protected]>

* Correction

Signed-off-by: rickbrouwer <[email protected]>

---------

Signed-off-by: rickbrouwer <[email protected]>

Author: rickbrouwer

config.toml

@@ -19,7 +19,7 @@ description = "Application autoscaling made simple"
 what_is = """
 **KEDA** is a [Kubernetes](https://kubernetes.io)-based Event Driven Autoscaler. With KEDA, you can drive the scaling of any container in Kubernetes based on the number of events needing to be processed.
 
-**KEDA** is a single-purpose and lightweight component that can be added into any Kubernetes cluster. KEDA works alongside standard Kubernetes components like the [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) and can extend functionality without overwriting or duplication. With KEDA you can explicitly map the apps you want to use event-driven scale, with other apps continuing to function.  This makes KEDA a flexible and safe option to run alongside any number of any other Kubernetes applications or frameworks.
+**KEDA** is a single-purpose and lightweight component that can be added into any Kubernetes cluster. KEDA works alongside standard Kubernetes components like the [Horizontal Pod Autoscaler](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/) and can extend functionality without overwriting or duplication. With KEDA, you can explicitly map the apps you want to use event-driven scale, with other apps continuing to function. This makes KEDA a flexible and safe option to run alongside any number of any other Kubernetes applications or frameworks.
 """
 
 locale = "en_US"
@@ -401,7 +401,7 @@ icon = "fas fa-bolt"
 
 [[params.features]]
 title = "Built-in Scalers"
-content = "Catalog of 50+ built-in scalers for various cloud platforms, databases, messaging systems, telemetry systems, CI/CD, and more"
+content = "Catalog of 70+ built-in scalers for various cloud platforms, databases, messaging systems, telemetry systems, CI/CD, and more"
 icon = "fas fa-cubes"
 
 [[params.features]]

content/docs/2.17/scalers/cron.md

@@ -32,7 +32,7 @@ triggers:
 > 💡 **Note:** `start`/`end` support ["Linux format cron"](https://en.wikipedia.org/wiki/Cron) (Minute Hour Dom Month Dow).
 
 > **Notice:**
-> **Start and end should not be same.**
+> **Start and end should not be the same.**
 >
 > For example, the following schedule is not valid:
 > ```yaml
@@ -52,13 +52,13 @@ What the CRON scaler does **not** do, is scale your workloads based on a recurri
 
 ### Scale to 0 during off hours
 
-If you want to scale you deployment to 0 outside office hours / working hours,
+If you want to scale your deployment to 0 outside office hours / working hours,
 you need to set `minReplicaCount: 0` in the ScaledObject, and increase the
 replicas during work hours. That way the Deployment will be scaled to 0 outside
 that time window. By default the ScaledObject `cooldownPeriod` is 5 minutes, so the actual
 scaling down will happen 5 minutes after the cron schedule `end` parameter.
 
-It's almost always an error to try to do the other way
+It's almost always an error to try to do it the other way
 around, i.e. set `desiredReplicas: 0` in the cron trigger.
 
 #### Example: scale up to 10 replicas from 6AM to 8PM and scale down to 0 replicas otherwise