From e787bd5d21742949dbdd39493a5a279fba6a3ee0 Mon Sep 17 00:00:00 2001 From: Giles Knap Date: Sun, 18 Feb 2024 15:16:22 +0000 Subject: [PATCH] typo --- docs/tutorials/setup_k8s_new_beamline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tutorials/setup_k8s_new_beamline.md b/docs/tutorials/setup_k8s_new_beamline.md index 236d6329..6c68d8dd 100644 --- a/docs/tutorials/setup_k8s_new_beamline.md +++ b/docs/tutorials/setup_k8s_new_beamline.md @@ -42,7 +42,7 @@ beamline by the cloud team and have requested access via the URL above. ## Create a new beamline repository -This step is almost exactly the same as [](create-new-beamline-local). Except that you will answer some of the questions in the copier template differently. In fact you can re-use the same repository you created in the previous tutorial and update the copier to change where we deploy the IOCs to. The following steps will guide you through this, but if you want to keep your old local beamline repo. The just follow the steps in [](create-new-beamline-local) but pick a new name and use the answers below. +This step is almost exactly the same as [](create-new-beamline-local). Except that you will answer some of the questions in the copier template differently. In fact you can re-use the same repository you created in the previous tutorial and update the copier to change where we deploy the IOCs to. The following steps will guide you through this, but if you want to keep your old local beamline repo, just follow the steps in [](create-new-beamline-local) but pick a new name and use the answers below. In order to change our original `bl01t` beamline to a Kubernetes beamline perform the following steps: