From a649da938f38ee5d1a2544a045ff5eebf81edc46 Mon Sep 17 00:00:00 2001
From: Norm Rasmussen <norman.rasmussen@me.com>
Date: Mon, 23 Oct 2023 11:25:52 -0400
Subject: [PATCH] Proof read and checked links for the neovim post. Ready to
 post.

---
 content/posts/mini_neovim.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/content/posts/mini_neovim.md b/content/posts/mini_neovim.md
index e42b56e..976d6ad 100644
--- a/content/posts/mini_neovim.md
+++ b/content/posts/mini_neovim.md
@@ -5,7 +5,7 @@ tags: ["neovim", "tools"]
 author: "Me"
 showToc: false
 TocOpen: false
-draft: true
+draft: false
 hidemeta: false
 description: 'Neovim is already super efficient and lightweight, but sometimes I need a barebones config for my servers and
 remote, miniature development environments.'
@@ -62,15 +62,15 @@ want to use the curly brackets in the final string that you use.
 1. Navigate to the machine/vm/server that you want to work on. For me, this VM doesn't have Neovim installed yet.
 2. [Install Neovim](https://github.com/neovim/neovim/wiki/Installing-Neovim)
 3. Clone your main repository to either your `.config` or your `.dotfiles` directory. And run a few commands:
-	* `git branch {branch-name}`
-	* `git checkout {branch-name}`
+ * `git branch {branch-name}`
+ * `git checkout {branch-name}`
 4. You'll now be in your branch, but everything will look the same. Start removing directories or files you don't need.
 5. Navigate to your plugins folder or `init.lua` that lists all your plugins and start hacking and slashing.
 6. Once you've saved all those files and you can open and close neovim without any plugin errors, you're ready to go.
 7. Navigate back to the root git directory and run a few more commands:
-	* `git add .`
-	* `git commit -m {Insert a detailed commit message of what you changed and updated.}`
-	* `git push {remote-name} {branch-name}`
+ * `git add .`
+ * `git commit -m {Insert a detailed commit message of what you changed and updated.}`
+ * `git push {remote-name} {branch-name}`
 8. And that's it! Go check your Github/Gitlab and check your branches and commits. You should see everything there! Congrats.
 
 For that last command, you can always check what your remote repo's push name is by running `git remote -v`. Most often, the name will be something like `origin` or `main`. If you saw [my post on having multiple remote repos]({{< ref "posts/multiple_git_remotes" >}}), you may something like "all". Just make sure to check before pushing!