From a2b60e4bcb498a8e69b48fdb24561b9d09b5df18 Mon Sep 17 00:00:00 2001 From: Jeong Jinwoo Date: Thu, 14 Sep 2023 20:52:11 +0900 Subject: [PATCH] docs(api): fix broken links --- site/content/en/docs/Reference/API/bases.md | 2 +- site/content/en/docs/Reference/API/images.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/site/content/en/docs/Reference/API/bases.md b/site/content/en/docs/Reference/API/bases.md index aecb477c2..9b4fdb711 100644 --- a/site/content/en/docs/Reference/API/bases.md +++ b/site/content/en/docs/Reference/API/bases.md @@ -20,5 +20,5 @@ You can run `kustomize edit fix` to automatically convert `bases` to `resources` Move entries into the [resources](/docs/reference/api/resources) field. This allows bases - which are still a -[central concept](/references/kustomize/glossary#base) - to be +[central concept](/docs/concepts/bases) - to be ordered relative to other input resources. diff --git a/site/content/en/docs/Reference/API/images.md b/site/content/en/docs/Reference/API/images.md index d2955bfa4..5f7fefe27 100644 --- a/site/content/en/docs/Reference/API/images.md +++ b/site/content/en/docs/Reference/API/images.md @@ -140,7 +140,7 @@ the image name is `foo` and an image was built for the source code at commit `1b then the container image would be `foo:1bb359ccce344ca5d263cd257958ea035c978fd3`. A simple way to push an image that was just built without manually updating the image tags is to -download the [kustomize standalone](https://github.com/kubernetes-sigs/kustomize/) tool and run +[download the kustomize standalone](/docs/getting-started/installation/) tool and run `kustomize edit set image` command to update the tags for you. **Example:** Set the latest git commit SHA as the image tag for `foo` images.