diff --git a/docs/docs/getting-started/first-steps.md b/docs/docs/getting-started/first-steps.md
index 6e685665c..a80ed7e1d 100644
--- a/docs/docs/getting-started/first-steps.md
+++ b/docs/docs/getting-started/first-steps.md
@@ -157,23 +157,10 @@ The following steps will guide you through the process of creating a cluster and
4. Create the cluster with one control-plane node and two worker nodes. `constellation create` uses options set in `constellation-conf.yaml` automatically.
-
-
-
```bash
- constellation create azure --control-plane-nodes 1 --worker-nodes 2 -y
+ constellation create --control-plane-nodes 1 --worker-nodes 2 -y
```
-
-
-
- ```bash
- constellation create gcp --control-plane-nodes 1 --worker-nodes 2 -y
- ```
-
-
-
-
This should give the following output:
```shell-session
diff --git a/docs/docs/workflows/create.md b/docs/docs/workflows/create.md
index 29ab2191f..73c4f245d 100644
--- a/docs/docs/workflows/create.md
+++ b/docs/docs/workflows/create.md
@@ -56,23 +56,10 @@ For more details, see the [verification section](../workflows/verify.md).
The following command creates a cluster with one control-plane and two worker nodes:
-
-
-
```bash
-constellation create azure --control-plane-nodes 1 --worker-nodes 2 -y
+constellation create --control-plane-nodes 1 --worker-nodes 2 -y
```
-
-
-
-```bash
-constellation create gcp --control-plane-nodes 1 --worker-nodes 2 -y
-```
-
-
-
-
For details on the flags and a list of supported instance types, consult the command help via `constellation create -h`.
*create* will store your cluster's configuration to a file named [`constellation-state.json`](../architecture/orchestration.md#installation-process) in your current directory.
diff --git a/docs/docs/workflows/verify.md b/docs/docs/workflows/verify.md
index 68a80dc96..ef9005404 100644
--- a/docs/docs/workflows/verify.md
+++ b/docs/docs/workflows/verify.md
@@ -22,23 +22,10 @@ Once measurements are configured, this command verifies an attestation statement
The following command performs attestation on the Constellation in your current workspace:
-
-
-
```bash
-constellation verify azure
+constellation verify
```
-
-
-
-```bash
-constellation verify gcp
-```
-
-
-
-
The command makes sure the value passed to `-cluster-id` matches the *clusterID* presented in the attestation statement.
This allows you to verify that you are connecting to a specific Constellation instance
Additionally, the confidential computing capabilities, as well as the VM image, are verified to match the expected configurations.
@@ -50,19 +37,6 @@ You can provide additional arguments for `verify` to verify any Constellation yo
* The IP address of a running Constellation's [VerificationService](../architecture/components.md#verification-service). The *VerificationService* is exposed via a NodePort service using the external IP address of your cluster. Run `kubectl get nodes -o wide` and look for `EXTERNAL-IP`.
* The Constellation's *clusterID*. See [cluster identity](../architecture/keys.md#cluster-identity) for more details.
-
-
-
```bash
-constellation verify azure -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ=
+constellation verify -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ=
```
-
-
-
-
-```bash
-constellation verify gcp -e 192.0.2.1 --cluster-id Q29uc3RlbGxhdGlvbkRvY3VtZW50YXRpb25TZWNyZXQ=
-```
-
-
-