From 4a00a820c8e8710eee376cf54804dcc8b7ef8f41 Mon Sep 17 00:00:00 2001
From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>
Date: Wed, 8 Feb 2023 09:26:16 +0000
Subject: [PATCH 1/2] Update: Provide more clarity about the term ANY time for
 initial development releases

## Description

The text `Anything MAY change at any time` can lead the idea that no rules are required and that PATCH releases can also introduces breaking changes or new functionalities when I understand that the whole idea here is clarifies that no compatible changes will be addressed in MINOR releases since the project has no MAJOR bumps at all.

So, could we please try to clarifies this one?
---
 semver.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/semver.md b/semver.md
index 53ea9a6..9f7735f 100644
--- a/semver.md
+++ b/semver.md
@@ -68,7 +68,9 @@ Each element MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0.
 MUST NOT be modified. Any modifications MUST be released as a new version.
 
 1. Major version zero (0.y.z) is for initial development. Anything MAY change
-at any time. The public API SHOULD NOT be considered stable.
+at any time. The public API SHOULD NOT be considered stable. Incompatible API changes and 
+new functionality might be introcuded in MINOR releases. PATCH releases still reserved
+to backwards compatible bug fixes.
 
 1. Version 1.0.0 defines the public API. The way in which the version number
 is incremented after this release is dependent on this public API and how it

From a20d6576a23010518e12eab746f40032e00d2011 Mon Sep 17 00:00:00 2001
From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>
Date: Wed, 8 Feb 2023 18:29:35 +0000
Subject: [PATCH 2/2] Apply suggestions from code review

---
 semver.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/semver.md b/semver.md
index 9f7735f..3117864 100644
--- a/semver.md
+++ b/semver.md
@@ -69,7 +69,7 @@ MUST NOT be modified. Any modifications MUST be released as a new version.
 
 1. Major version zero (0.y.z) is for initial development. Anything MAY change
 at any time. The public API SHOULD NOT be considered stable. Incompatible API changes and 
-new functionality might be introcuded in MINOR releases. PATCH releases still reserved
+new functionality might be introduced in incremental `0.Y.0` releases when `0.Y.Z` releases still reserved
 to backwards compatible bug fixes.
 
 1. Version 1.0.0 defines the public API. The way in which the version number