From 212773764a61a5fd564bb0309cd9b5c9ca193244 Mon Sep 17 00:00:00 2001
From: Bryan Finster <bryan.finster@gmail.com>
Date: Mon, 17 Jul 2023 08:33:11 -0500
Subject: [PATCH] Add Texan translation (#312)

---
 .linkinator.config.json     | 14 +++++++-------
 content/MinimumCD/_index.md |  4 ++--
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/.linkinator.config.json b/.linkinator.config.json
index fc017df..c70a9a9 100644
--- a/.linkinator.config.json
+++ b/.linkinator.config.json
@@ -1,8 +1,8 @@
 {
-    "recurse": true,
-    "skip": "^(https://.*linkedin.com),^(https://.*twitter.com),(/immutable),(/tbd)",
-    "verbosity": "error",
-    "timeout": 0,
-    "markdown": true,
-    "directoryListing": true
-  }
\ No newline at end of file
+  "recurse": true,
+  "skip": "^(https://.*linkedin.com),^(https://.*twitter.com),^(https://github.com/Minimum-CD*)",
+  "verbosity": "error",
+  "timeout": 0,
+  "markdown": true,
+  "directoryListing": true
+}
\ No newline at end of file
diff --git a/content/MinimumCD/_index.md b/content/MinimumCD/_index.md
index 9c56267..71997c3 100644
--- a/content/MinimumCD/_index.md
+++ b/content/MinimumCD/_index.md
@@ -37,7 +37,7 @@ The minimum activities required for CD are:
   is the only way to deploy to any environment
 - The pipeline decides the releasability of changes, its verdict is [definitive](../faq/#why-should-the-pipeline-be-definitive-for-deploy)
 - Artifacts created by the pipeline always meet the organization's [definition of deployable](../faq/#what-do-we-mean-by-definition-of-deployable)
-- [Immutable artifact](./immutable) (no human changes after commit)
+- [Immutable artifact](../minimumcd/immutable/) (no human changes after commit)
 - All feature work stops when the pipeline is red
 - Production-like test environment
 - Rollback on-demand
@@ -58,7 +58,7 @@ The minimum activities required for CI are:
 
 ## Trunk-based Development
 
-[Trunk-based development](./tbd) is the branching pattern required to meet the definition
+[Trunk-based development](../minimumcd/tbd) is the branching pattern required to meet the definition
 of CI. It prevents lost work, the risk of corruption that comes from merge conflict resolution, and also reduces movement
 waste that increases batch size.