Update getting started for capa and capz releases (#2268)

* Update getting started for capa and capz releases

* Add azure releases link

src/content/vintage/getting-started/create-workload-cluster/index.md

@@ -88,13 +88,14 @@ For backward compatibility, vintage cluster templating does not require the `--n
 {{< /tab >}}
 {{< tab id="cluster-capa-ec2" for-impl="capa_ec2">}}
 
-This will automatically use the latest release of the relevant Helm chart [cluster-aws](https://github.com/giantswarm/cluster-aws/blob/master/CHANGELOG.md):
+[Choose a release version here](https://docs.giantswarm.io/changes/workload-cluster-releases-for-capa/), or use `kubectl gs get releases`, and fill it into this example command:
 
 ```sh
 kubectl gs template cluster \
   --provider capa \
   --name mycluster \
   --organization testing \
+  --release 28.0.0 `# please fill in your desired release version` \
   > cluster.yaml
 ```
 
@@ -106,6 +107,7 @@ kubectl gs template cluster \
   --provider capa \
   --name mycluster \
   --organization testing \
+  --release 28.0.0 `# please fill in your desired release version` \
   --aws-cluster-role-identity-name=dev-account-role-identity
   > cluster.yaml
 ```
@@ -142,7 +144,7 @@ If no `aws-cluster-role-identity-name` is passed, then we assume a `AWSClusterRo
 {{< /tab >}}
 {{< tab id="cluster-capz-azure-vms" for-impl="capz_vms">}}
 
-This will automatically use the latest release of the relevant Helm chart [cluster-azure](https://github.com/giantswarm/cluster-azure/blob/master/CHANGELOG.md):
+[Choose a release version here](https://docs.giantswarm.io/changes/workload-cluster-releases-for-azure/), or use `kubectl gs get releases`, and fill it into this example command:
 
 ```sh
 kubectl gs template cluster \
@@ -151,6 +153,7 @@ kubectl gs template cluster \
   --organization testing \
   --region westeurope \
   --azure-subscription-id 00000000-0000-0000-0000-000000000000 `# fill in your subscription ID` \
+  --release 28.0.0 `# please fill in your desired release version` \
   > cluster.yaml
 ```
 
@@ -374,6 +377,6 @@ kubectl gs update app \
 
 ### Updating a cluster
 
-Cluster updates can be easily performed straight away or scheduled for a specific moment in time. The latter is a feature in the vintage product family that many customers find very useful because it allows them to schedule updates without the need to physically be there to "press the button".
+Cluster updates can be easily performed straight away or scheduled for a specific moment in time. The latter is a feature that many customers find very useful because it allows them to schedule updates without the need to physically be there to "press the button".
 
 More information on updating a cluster can be found [in the kubectl-gs reference]({{< relref "/vintage/use-the-api/kubectl-gs/update-cluster" >}}).