From 37ae91ac720967ad809f818e12f0c65a7fd94338 Mon Sep 17 00:00:00 2001 From: Moritz Wiesinger Date: Mon, 11 Dec 2023 14:27:07 +0100 Subject: [PATCH] refactor links containing dashes Signed-off-by: Moritz Wiesinger --- docs-new/docs/contribute/general/dco.md | 4 ++-- docs-new/docs/core-concepts/usecase-orchestrate.md | 8 ++++---- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs-new/docs/contribute/general/dco.md b/docs-new/docs/contribute/general/dco.md index d80e5c8587..e2ce3e6322 100644 --- a/docs-new/docs/contribute/general/dco.md +++ b/docs-new/docs/contribute/general/dco.md @@ -72,13 +72,13 @@ Your builds will fail and can not be merged if the DCO check fails. Do any of the following to implement the DCO signoff on each commit: -* [Add **-s** or **--signoff**](#sign-off-with-git-commit--s) +* [Add **-s** or **--signoff**](#sign-off-while-committing) to your usual `git commit` commands * [Manually add text](#manually-add-text-to-commit-description) to your commit body * [Automate DCO](#automate-dco) -## Sign off with git commit -s +## Sign off while committing Use the **-s** or **--signoff** flag to the `git commit` command to sign off on a commit. diff --git a/docs-new/docs/core-concepts/usecase-orchestrate.md b/docs-new/docs/core-concepts/usecase-orchestrate.md index 6eabaac04c..15f33adcd3 100644 --- a/docs-new/docs/core-concepts/usecase-orchestrate.md +++ b/docs-new/docs/core-concepts/usecase-orchestrate.md @@ -47,8 +47,8 @@ example. The steps to implement pre- and post-deployment orchestration are: * [Using this exercise](#using-this-exercise) -* [Define evaluations to be performed pre- and post-deployment](#define-evaluations-to-be-performed-pre--and-post-deployment) -* [Define tasks to be performed pre- and post-deployment](#define-tasks-to-be-performed-pre--and-post-deployment) +* [Define evaluations to be performed pre- and post-deployment](#define-evaluations-to-be-performed-prepost-deployment) +* [Define tasks to be performed pre- and post-deployment](#define-tasks-to-be-performed-prepost-deployment) * [Integrate evaluations and tasks into the cluster](#integrate-evaluations-and-tasks-into-the-cluster) This is the third of three exercises in the @@ -82,7 +82,7 @@ you need to do the following: which aggregate [workloads](https://kubernetes.io/docs/concepts/workloads/) that are combined into the released product, regardless of the tools being used. -## Define evaluations to be performed pre- and post-deployment +## Define evaluations to be performed pre/post deployment An `evaluation` is a KeptnMetric that has a defined target value. Evaluations are resources that are defined in a @@ -115,7 +115,7 @@ The `evaluationTarget` is set to be `>4`, so this evaluation makes sure that more than 4 CPUs are available. You could include objectives and additional metrics in this evaluation. -## Define tasks to be performed pre- and post-deployment +## Define tasks to be performed pre/post deployment Tasks are resources that are defined in a [KeptnTaskDefinition](../reference/crd-reference/taskdefinition.md)