diff --git a/content/crds-api-reference/extensions.md b/content/crds-api-reference/extensions.md
index d172ed919..c12429198 100644
--- a/content/crds-api-reference/extensions.md
+++ b/content/crds-api-reference/extensions.md
@@ -20,7 +20,7 @@ Before you create an Extension CR, you need to modify the Integration Config res
       namespace: openshift-operators
 ```
 
-The above configuration will whitelist the `EnvironmentProvisioner` CRD and blacklist the `ResourceQuota` resource. Also note that the `namespace` field is mandatory and should be set to the namespace where the ArgoCD is deployed.
+The above configuration will allow the `EnvironmentProvisioner` CRD and blacklist the `ResourceQuota` resource. Also note that the `namespace` field is mandatory and should be set to the namespace where the ArgoCD is deployed.
 
 Every Extension CR is associated with a specific Tenant. Here's an example of an Extension CR that is associated with a Tenant named `tenant-sample`:
 
diff --git a/content/tutorials/tenant/assigning-metadata.md b/content/tutorials/tenant/assigning-metadata.md
index 8cdcb8e47..d33ae192a 100644
--- a/content/tutorials/tenant/assigning-metadata.md
+++ b/content/tutorials/tenant/assigning-metadata.md
@@ -117,4 +117,4 @@ spec:
 
 This setup ensures that all sandbox namespaces receive the designated metadata, with support for templated values, such as **{{ TENANT.USERNAME }}**, allowing dynamic customization based on the tenant or user context.
 
-These enhancements in metadata management within the `v1beta3` version of the Tenant CR provide comprehensive and flexible tools for labeling and annotating namespaces, supporting a wide range of organizational, security, and operational objectives.
\ No newline at end of file
+These enhancements in metadata management within the `v1beta3` version of the Tenant CR provide comprehensive and flexible tools for labeling and annotating namespaces, supporting a wide range of organizational, security, and operational objectives.
diff --git a/content/tutorials/tenant/create-tenant.md b/content/tutorials/tenant/create-tenant.md
index 2335035c0..f1de2b7a2 100644
--- a/content/tutorials/tenant/create-tenant.md
+++ b/content/tutorials/tenant/create-tenant.md
@@ -1,6 +1,6 @@
 # Creating a Tenant
 
-Bill, a cluster admin, has been tasked by the CTO of NordMart to set up a new tenant for Anna's team. Following the request, Bill proceeds to create a new tenant named bluesky in the Kubernetes cluster.
+Bill, a cluster admin, has been tasked by the CTO of Nordmart to set up a new tenant for Anna's team. Following the request, Bill proceeds to create a new tenant named bluesky in the Kubernetes cluster.
 
 ## Setting Up the Tenant
 
diff --git a/content/tutorials/tenant/creating-namespaces.md b/content/tutorials/tenant/creating-namespaces.md
index f9d27b425..32b21ffd0 100644
--- a/content/tutorials/tenant/creating-namespaces.md
+++ b/content/tutorials/tenant/creating-namespaces.md
@@ -2,7 +2,6 @@
 
 Bill, tasked with structuring namespaces for different environments within a tenant, utilizes the Tenant Custom Resource (CR) to streamline this process efficiently. Here's how Bill can orchestrate the creation of `dev`, `build`, and `production` environments for the tenant members directly through the Tenant CR.
 
-
 ## Strategy for Namespace Creation
 
 To facilitate the environment setup, Bill decides to categorize the namespaces based on their association with the tenant's name. He opts to use the `namespaces.withTenantPrefix` field for namespaces that should carry the tenant name as a prefix, enhancing clarity and organization. For namespaces that do not require a tenant name prefix, Bill employs the `namespaces.withoutTenantPrefix` field.