diff --git a/docs/docs/architecture/services.md b/docs/docs/architecture/services.md
index 45389ef2d..c5bac1264 100644
--- a/docs/docs/architecture/services.md
+++ b/docs/docs/architecture/services.md
@@ -1,8 +1,4 @@
-# Components
-
-
-
-(**FS: Overall, good. Should be renamed to something like "Kubernetes Components"**)
+# Constellation services
 
 Constellation takes care of bootstrapping and initializing a Confidential Kubernetes cluster. (**FS: weird**)
 During the lifetime of the cluster, it handles day 2 operations such as key management, remote attestation, and updates. (**FS: features**)
@@ -36,15 +32,6 @@ flowchart LR
     C -- deploys --> F
 ```
 
-## Bootstrapper
-
-**FS: some context missing**
-The *Bootstrapper* is the first component launched after booting a Constellation node image.
-It sets up that machine as a Kubernetes node and integrates that node into the Kubernetes cluster.
-To this end, the *Bootstrapper* first downloads and [verifies](https://blog.sigstore.dev/kubernetes-signals-massive-adoption-of-sigstore-for-protecting-open-source-ecosystem-73a6757da73) (**FS: this is not a good link**) the [Kubernetes components](https://kubernetes.io/docs/concepts/overview/components/) at the configured versions. (**FS: where are they configured?**)
-The *Bootstrapper* tries to find an existing cluster (**FS: how?**) and if successful, communicates with the [JoinService](components.md#joinservice) to join the node.
-Otherwise, it waits for an initialization request to create a new Kubernetes cluster.
-
 ## JoinService
 
 The *JoinService* runs as [DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) on each control-plane node (**FS: should we define control-plane somewhere?**).