From 5a995f7e276151bb39e1dd31b25c1133c94b0ab9 Mon Sep 17 00:00:00 2001
From: Paul Hatcherian <1835615+PaulHatch@users.noreply.github.com>
Date: Wed, 9 Aug 2023 08:59:50 -0400
Subject: [PATCH] Update guide

---
 guide.md | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/guide.md b/guide.md
index 04f7a40..7a9936e 100644
--- a/guide.md
+++ b/guide.md
@@ -1,5 +1,6 @@
 # Configuration Guide
 
+WIP
 
 ## Choosing a Release Strategy
 
@@ -25,19 +26,14 @@ The only real limitation of this strategy is that it does not allow for multiple
 
 Tags should generally not be created automatically as part of the build, which can cause strange behavior unless you've taken care to prevent race conditions. Creating tags automatically also largely negates the purpose of this strategy as only build automated test.
 
+ > Remaining strategies are still a work in progress.
 
 ## Branch Versioning
 
 Moving past tag versioning is where things get a little more complicated, as there are many different ways to version branches.
+
 ### Version Branches with Tag Versioning
-
-It is possible to use version branches while still
-
-
 ### Version from Branch Name (Non-Predictive)
-
-
-
 ### Version from Branch Name (Predictive)
 
 ## Branch Versioning: GitFlow