Fix: typos (#7995)

* Update faqs.md

* Update rate-limiting.md

* Update env.md

* Update custom-entities.md

app/_src/deck/faqs.md

@@ -87,7 +87,7 @@ upgrading to decK 1.12 to take advantage of the new `--konnect` CLI flags.
 ### I use Cassandra as a data store for Kong, can I use decK?
 
 As of {{site.base_gateway}} 3.4, you can't use Cassandra as a data store, 
-as it is longer supported by Kong.
+as it is no longer supported by Kong.
 
 You can use decK with earlier versions of Kong backed by Cassandra.
 However, if you observe errors during a sync process, you will have to

app/_src/gateway/kong-enterprise/secrets-management/backends/env.md

@@ -35,7 +35,7 @@ This allows you to reference the secrets separately:
 ```
 
 {:.note}
-> When adding an environment variable with Helm, ensure that the variable being passed has `kong-` appended to it. 
+> When adding an environment variable with Helm, ensure that the variable being passed has `kong-` prepended to it. 
 
 ## Configuration via vaults entity
 

app/_src/gateway/plugin-development/custom-entities.md

@@ -60,7 +60,7 @@ containing the initial migrations. We'll see how this is done in a minute.
 Sometimes it is necessary to introduce changes after a version of a plugin has already been
 released. A new functionality might be needed. A database table row might need changing.
 
-When this happens, *you must* create a new migrations file. You *must not* of modify the
+When this happens, *you must* create a new migrations file. You *must not* modify the
 existing migration files once they are published (you can still make them more robust and
 bulletproof if you want, e.g. always try to write the migrations reentrant).
 

app/_src/kubernetes-ingress-controller/get-started/rate-limiting.md

@@ -13,7 +13,7 @@ Rate limiting is used to control the rate of requests sent to an upstream servic
 
 ## Create a rate-limiting KongPlugin
 
-Configuring plugins with {{ site.kic_product_name }} is different compared to how you'd do it with {{ kic.base_gateway }}. Rather than attaching a configuration directly to a service or route, you create a `KongPlugin` definition and then annotate your Kubernetes resource with the `konghq.com/plugins` annotation.
+Configuring plugins with {{ site.kic_product_name }} is different compared to how you'd do it with {{ site.base_gateway }}. Rather than attaching a configuration directly to a service or route, you create a `KongPlugin` definition and then annotate your Kubernetes resource with the `konghq.com/plugins` annotation.
 
 {:.note}
 > This tutorial uses the [Rate Limiting](/hub/kong-inc/rate-limiting/) <span class="badge free"></span> plugin. The [Rate Limiting Advanced](/hub/kong-inc/rate-limiting-advanced) <span class="badge enterprise"></span> plugin is also available. The advanced version provides additional features such as support for the sliding window algorithm and advanced Redis support for greater performance.