From 3ed0c734696daece3be46bdf0bc4602698b487ef Mon Sep 17 00:00:00 2001
From: Andrew Arz <149685528+aarz-snl@users.noreply.github.com>
Date: Fri, 12 Jan 2024 11:53:15 -0500
Subject: [PATCH] Update upgrading.md to account for 1.3.1 (#151)

* Update upgrading.md

* Update upgrading.md
---
 docs/markdown/maintenance/upgrading.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/markdown/maintenance/upgrading.md b/docs/markdown/maintenance/upgrading.md
index 78ac8242..3622ccd6 100644
--- a/docs/markdown/maintenance/upgrading.md
+++ b/docs/markdown/maintenance/upgrading.md
@@ -159,7 +159,7 @@ The deploy.sh script should have now created new files on the Linux server at lo
 
 Then reboot your Client computers & Windows Event Collector. On Windows Event Collector open services.msc as an administrator and make sure the winlogbeat service is set to start automatically, and is running.
 
+## 7. Upgrade from 1.3.0 to 1.3.1
 
-
-
+This is a hotfix to the install script and some additional troubleshooting steps added to documentation on space management. Unless you're encountering problems with your current installation, or if your logs are running out of space, there's no need to upgrade to version 1.3.1, as it doesn't offer any additional functionality changes.