diff --git a/data/faq.toml b/data/faq.toml
index c94e198d..489bf50a 100644
--- a/data/faq.toml
+++ b/data/faq.toml
@@ -69,7 +69,7 @@ client](https://godoc.org/k8s.io/client-go/dynamic) from the `client-go` package
 [GroupVersionResource](https://godoc.org/k8s.io/apimachinery/pkg/runtime/schema#GroupVersionResource)
 describing the type of resource to be accessed and returns a
 [NamespaceableResourceInterface](https://godoc.org/k8s.io/client-go/dynamic#NamespaceableResourceInterface)
-which contains methods to retrieve, create, or maniuplate that resource.  Here's a code sample
+which contains methods to retrieve, create, or manipulate that resource.  Here's a code sample
 containing a function that retrieves a KEDA `ScaledObject` resource by name.
 
 ```go
diff --git a/data/faq20.toml b/data/faq20.toml
index 79f2b49a..5e9f43ef 100644
--- a/data/faq20.toml
+++ b/data/faq20.toml
@@ -42,7 +42,7 @@ KEDA allows you to use multiple triggers as part of the same `ScaledObject` or `
 
 By doing this, your autoscaling becomes better:
 - All your autoscaling rules are in one place
-- You will not have multiple `ScaledObject`'s or `ScaledJob`'s interferring with each other
+- You will not have multiple `ScaledObject`'s or `ScaledJob`'s interfering with each other
 
 KEDA will start scaling as soon as when one of the triggers meets the criteria. Horizontal Pod Autoscaler (HPA) will calculate metrics for every scaler and use the highest desired replica count to scale the workload to.
 """
diff --git a/layouts/404.html b/layouts/404.html
index 1654f3b1..1d5dd18b 100644
--- a/layouts/404.html
+++ b/layouts/404.html
@@ -7,7 +7,7 @@
             Woops! Dead link...
           </p>
 
-        That's not very conventient, sorry about that!
+        That's not very convenient, sorry about that!
 
         Maybe you were looking for:
         <ul>