From 95dd9a459e3cb6e94b2e2391b59bea833e1008fe Mon Sep 17 00:00:00 2001
From: Paul Ebose <paulebose@gmail.com>
Date: Fri, 9 Aug 2024 15:09:09 +0100
Subject: [PATCH] fix spacing in readme

---
 README.md | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/README.md b/README.md
index 8c0da11..3f92a2f 100644
--- a/README.md
+++ b/README.md
@@ -217,19 +217,19 @@ GitHub Actions allows users to select a specific version of the action to use,
 based on release tags. This script simplifies this process by performing the
 following steps:
 
-1. **Retrieving the latest release tag:** The script starts by fetching the
-   most recent semver release tag of the current branch, by looking at the
-   local data available in your repository.
-1. **Prompting for a new release tag:** The user is then prompted to enter a
-   new release tag. To assist with this, the script displays the tag retrieved
-   in the previous step, and validates the format of the inputted tag (vX.X.X).
-   The user is also reminded to update the version field in package.json.
-1. **Tagging the new release:** The script then tags a new release and syncs
-   the separate major tag (e.g. v1, v2) with the new release tag
-   (e.g. v1.0.0, v2.1.2). When the user is creating a new major release, the
-   script auto-detects this and creates a `releases/v#` branch for the previous
-   major version.
+1. **Retrieving the latest release tag:** The script starts by fetching the most
+   recent semver release tag of the current branch, by looking at the local data
+   available in your repository.
+1. **Prompting for a new release tag:** The user is then prompted to enter a new
+   release tag. To assist with this, the script displays the tag retrieved in
+   the previous step, and validates the format of the inputted tag (vX.X.X). The
+   user is also reminded to update the version field in package.json.
+1. **Tagging the new release:** The script then tags a new release and syncs the
+   separate major tag (e.g. v1, v2) with the new release tag (e.g. v1.0.0,
+   v2.1.2). When the user is creating a new major release, the script
+   auto-detects this and creates a `releases/v#` branch for the previous major
+   version.
 1. **Pushing changes to remote:** Finally, the script pushes the necessary
-   commits, tags and branches to the remote repository. From here, you will
-   need to create a new release in GitHub so users can easily reference the
-   new tags in their workflows.
+   commits, tags and branches to the remote repository. From here, you will need
+   to create a new release in GitHub so users can easily reference the new tags
+   in their workflows.