diff --git a/content/KubernetesOperators/BackingServices/_index.md b/content/KubernetesOperators/BackingServices/_index.md
index 19deb82eedc522b6a83d0187d69fafcacece5e33..4da695dff3b94a14bd2361affa69f6a891162520 100644
--- a/content/KubernetesOperators/BackingServices/_index.md
+++ b/content/KubernetesOperators/BackingServices/_index.md
@@ -17,7 +17,7 @@ cat << EOF | kubectl apply -f -
 apiVersion: "acid.zalan.do/v1"
 kind: postgresql
 metadata:
-  name: nexctloud-postgres
+  name: nextcloud-postgres
   namespace: fight-marketing
 spec:
   teamId: "nextcloud"
diff --git a/content/ProblemToSolve/TheExample/_index.md b/content/ProblemToSolve/TheExample/_index.md
index f479f1700a43e73dfa4629992e0056baba86bda0..916fd89a3e65ef601607feb122e984d77bd14a9f 100644
--- a/content/ProblemToSolve/TheExample/_index.md
+++ b/content/ProblemToSolve/TheExample/_index.md
@@ -5,15 +5,14 @@ weight: 3
 
 Heard about [Nextcloud](https://nextcloud.com/)? Let's say that we want to deploy a Nextcloud instance for a nice association fighting marketing.
 
-Before deploying the Nextlcoud, we'll need to list the backing services that would be necessary:
+Before deploying the Nextcloud, we'll need to list the backing services that would be necessary:
 
  - postgres database
  - redis cache
- - smtp relay to send email notification
+ - smtp relay to send email notifications
  - S3 compatible API for object store
  - OpenIdConnect provider for Single Sign On
  - libre office online
- - nextant
 
 This is to deploy a reliable and scalable Nextcloud instance. For the sake of simplicity, let's say that we just need Postgres. But keep in mind, that we have the other backing services in mind too, and that we can use the same paradigms.