kcon2025/workshop: fix links (#17)

* kcon2025/workshop: fix links

* kcon2025/workshop: other minor docs fixes

Author: gman0

20250401-kubecon-london/workshop/00-prerequisites/01-install.sh

@@ -28,7 +28,7 @@ fi
 
 if [[ ! -f "${WORKSHOP_ROOT}/bin/.checkpoint-mcp-example-crd" ]]; then
     echo "🚀 Downloading KCP's mcp-example-crd"
-    curl -L "https://github.com/mjudeikis/kcp-multicluster-provider-example/releases/download/v0.0.4/kcp-multicluster-provider-example_0.0.4_${GOOS}_${GOARCH}.tar.gz" \
+    curl -L "https://github.com/kcp-dev/contrib/releases/download/v1-kubecon2025-london/contrib_1-kubecon2025-london_${GOOS}_${GOARCH}.tar.gz" \
       | tar -C "${WORKSHOP_ROOT}/bin" -xzf - mcp-example-crd
     touch "${WORKSHOP_ROOT}/bin/.checkpoint-mcp-example-crd"
 fi

20250401-kubecon-london/workshop/00-prerequisites/README.md

@@ -37,7 +37,7 @@ Ready for a warm-up? In this quick exercise we are going to install programs we'
 
 * [kcp](https://github.com/kcp-dev/kcp/releases/latest),
 * kcp's [api-syncagent](https://github.com/kcp-dev/api-syncagent/releases/latest),
-* kcp's [multicluster-controller runtime example binary](https://github.com/mjudeikis/kcp-multicluster-provider-example/releases/download),
+* kcp's [multicluster-controller runtime example binary](https://github.com/kcp-dev/contrib/releases/tag/v1-kubecon2025-london),
 * [kind](https://github.com/kubernetes-sigs/kind/releases/latest),
 * [kubectl](https://kubernetes.io/docs/tasks/tools/),
 * and, [kubectl-krew](https://krew.sigs.k8s.io/docs/user-guide/setup/install/).
@@ -64,4 +64,4 @@ Done already? High-five! Check-in your completion with:
 00-prerequisites/99-highfive.sh
 ```
 
-If there were no errors, you may continue with the next exercise.
+If there were no errors, you may continue with [the next exercise 🔥](/contrib/learning/20250401-kubecon-london/workshop/01-deploy-kcp/)!

20250401-kubecon-london/workshop/01-deploy-kcp/README.md

@@ -55,7 +55,7 @@ Once kcp's output seems stable, we can start making simple kubectl calls against
         ```fish
         set -gx WORKSHOP_ROOT (git rev-parse --show-toplevel)/20250401-kubecon-london/workshop
         set -gx PATH $WORKSHOP_ROOT/bin $PATH
-        set -gx KUBECONFIG $WORKSHOP_ROOT/.kcp/admin.kubeconfig"
+        set -gx KUBECONFIG $WORKSHOP_ROOT/.kcp/admin.kubeconfig
         ```
 
 The following command should work now:
@@ -86,7 +86,7 @@ Finished? High-five! Check-in your completion with:
 01-deploy-kcp/99-highfive.sh
 ```
 
-If there were no errors, you may continue with the next exercise.
+If there were no errors, you may continue with [the next exercise 🔥](/contrib/learning/20250401-kubecon-london/workshop/02-explore-workspaces/)!
 
 ### Cheat-sheet
 

20250401-kubecon-london/workshop/02-explore-workspaces/README.md

@@ -321,7 +321,7 @@ Finished? High-five! Check-in your completion with:
 02-explore-workspaces/99-highfive.sh
 ```
 
-If there were no errors, you may continue with the next exercise.
+If there were no errors, you may continue with [the next exercise 🔥](/contrib/learning/20250401-kubecon-london/workshop/03-dynamic-providers/)!
 
 ### Cheat-sheet
 

20250401-kubecon-london/workshop/03-dynamic-providers/README.md

@@ -33,7 +33,7 @@ Excited? Let's get down to it!
         set -gx EXERCISE_DIR $WORKSHOP_ROOT/03-dynamic-providers
         set -gx KUBECONFIGS_DIR $WORKSHOP_ROOT/kubeconfigs
         set -gx KREW_ROOT $WORKSHOP_ROOT/bin/.krew
-        set -gx PATH $WORKSHOP_ROOT/bin/.krew/bin $WORKSHOP_ROOT/bin $PATH"
+        set -gx PATH $WORKSHOP_ROOT/bin/.krew/bin $WORKSHOP_ROOT/bin $PATH
         ```
 
 Surprise! You've just been appointed as the owner of a company responsible for running PostgreSQL databases, **SQL<sup>3</sup> Co.**! What's worse, you haven't heard of kcp yet! What you did hear of though is that PostgreSQL servers need compute and storage. And that Kubernetes can do all of that. So, to get things going, let's start up a [kind](https://kind.sigs.k8s.io/)-backed Kubernetes cluster:
@@ -353,7 +353,7 @@ Finished? High-five! Check-in your completion with:
 03-dynamic-providers/99-highfive.sh
 ```
 
-If there were no errors, you may continue with the next exercise.
+If there were no errors, you may continue with [the next exercise 🔥](/contrib/learning/20250401-kubecon-london/workshop/04-application-providers/)!
 
 ### Cheat-sheet
 

20250401-kubecon-london/workshop/04-application-providers/README.md

@@ -4,7 +4,7 @@ title: "04: Application providers"
 
 # Application providers
 
-In our last exercise of this workshop we'll take a look at a kcp-native application, that uses [sigs.k8s.io/multicluster-runtime](https://github.com/kubernetes-sigs/multicluster-runtime) to run a kcp provider, and reconciles the deployment across workspaces.
+In our last exercise of this workshop we'll take a look at a kcp-native application that uses [sigs.k8s.io/multicluster-runtime](https://github.com/kubernetes-sigs/multicluster-runtime) to run a kcp provider, and reconciles the deployment across workspaces.
 
 ## Going native
 
@@ -13,12 +13,12 @@ After the great kick-off with the PostgreSQL-as-a-Service business, the folks ba
 To accomplish that, they say all they had to use was:
 
 * [kubebuilder](https://github.com/kubernetes-sigs/kubebuilder) to scaffold the project and CRDs,
-* [sigs.k8s.io/multicluster-runtime](https://github.com/kubernetes-sigs/multicluster-runtime) to provide multicluster manager, controller and reconciler functionalities,
-* [github.com/kcp-dev/multicluster-provider/virtualworkspace]() to interact with kcp virtual workspaces,
-* [github.com/kcp-dev/kcp/sdk]() to add in kcp schemas,
+* [sigs.k8s.io/multicluster-runtime](https://sigs.k8s.io/multicluster-runtime) to provide multicluster manager, controller and reconciler functionalities,
+* [github.com/kcp-dev/multicluster-provider](https://github.com/kcp-dev/multicluster-provider) to interact with kcp virtual workspaces,
+* [github.com/kcp-dev/kcp/sdk](https://github.com/kcp-dev/kcp/tree/main/sdk) to add in kcp schemas,
 * and lastly, [github.com/cloudnative-pg/cloudnative-pg](https://github.com/cloudnative-pg/cloudnative-pg) to be able to work with _postgresql.cnpg.io_ resources.
 
-We won't go into any implementation details here, but you are very welcome to inspect and play around with the code yourself at <>. The kcp-aware bits are clearly marked to see what multicluster bits need to be added into the kubebuilder-generated base. As far as the complexity goes, we hope you will find it quite underwhelming :)
+We won't go into any implementation details here, but you are very welcome to inspect and play around with the code yourself at <https://github.com/kcp-dev/contrib/tree/main/20250401-kubecon-london/workshop/kcp-multicluster-provider-example>. The kcp-aware bits are clearly marked to see what multicluster bits need to be added into the kubebuilder-generated base. As far as the complexity goes, we hope you will find it quite underwhelming :)
 
 ## There is an App in my WS! 🤌
 
@@ -89,7 +89,7 @@ It references the database we've created earlier, and the Secret with credential
 ```shell title="Starting the mcp-app"
 kubectl ws use :root:providers:application
 mcp-example-crd --server=$(kubectl get apiexport apis.contrib.kcp.io -o jsonpath="{.status.virtualWorkspaces[0].url}") \
-  --provider-kubeconfig ${KUBECONFIGS_DIR}/provider.kubeconfig
+  --provider-kubeconfig $KUBECONFIGS_DIR/provider.kubeconfig
 ```
 
 !!! Important