update workflow deploy only

equinor · Aug 24, 2023 · 0bf9459 · 0bf9459
1 parent ef338fe
commit 0bf9459
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/public-site/docs/src/guides/deploy-only/index.md b/public-site/docs/src/guides/deploy-only/index.md
@@ -27,7 +27,7 @@ Unlike a regular Radix application, for a deploy-only application you have two o
 - The GitHub repository which act as a pure configuration repository. That is, source code for the different components resides in other repositories
 - The `radixconfig.yaml` is in the source code repository
 
-The documentation will use the second option and this [example repository](https://github.com/equinor/radix-example-arm-template)
+The documentation will use the second option.
 
 ## The `radixconfig.yaml` file
 

diff --git a/public-site/docs/src/guides/deployment-promotion/index.md b/public-site/docs/src/guides/deployment-promotion/index.md
@@ -24,7 +24,7 @@ To promote a deployment you must create a new Job of type `promote`. There are s
 
 ## Promote to another environment
 
-Taking the current active deployment from one environment into another is an effective workflow; it can be used as a manual "deploy-to-production" step if you prefer to not map the production environment to a git branch for deployment. The [workflows](../workflows/) guide has an example of how to use this.
+Taking the current active deployment from one environment into another is an effective workflow; it can be used as a manual "deploy-to-production" step if you prefer to not map the production environment to a git branch for deployment. The [workflows](../../start/workflows/) guide has an example of how to use this.
 
 ## Promote an old deployment/rollback