From 6ffc7565eebf050ddb73111c6be0871798cb732d Mon Sep 17 00:00:00 2001 From: Kingdon Barrett Date: Mon, 21 Aug 2023 14:32:01 -0400 Subject: [PATCH] This commit should fail Add a bad link id anchor that doesn't go anywhere (but isn't a 404) Signed-off-by: Kingdon Barrett --- content/en/flux/flux-e2e.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/flux/flux-e2e.md b/content/en/flux/flux-e2e.md index f8d1f42c6..38b0e30a7 100644 --- a/content/en/flux/flux-e2e.md +++ b/content/en/flux/flux-e2e.md @@ -11,7 +11,7 @@ Note that this guide has not been updated since more than a year ago. It does no Expect this doc to receive an overhaul soon. {{% /alert %}} -Below we describe the flow of data through Flux, from End to End. +below we describe the flow of data through flux, from end to end. [here is a link that doesn't go anywhere](#id-anchor-failure) We assume a standard Flux installation, with all optional features enabled, then explain how Flux users can expect their change to flow through the stages of its life as a commit, and describe how the commit data passes through the Flux system and the cluster, in rough chronological order. We tried to cover