Updates following Review from jerboaa

Signed-off-by: Stewart X Addison <[email protected]>

content/blog/early-access-builds-feb2024/index.md

@@ -30,8 +30,8 @@ these builds.
 
 By building and providing these early access builds from tags instead of the
 head of the default branch we can more easily work with the upstream openjdk
-project to identify the contents of a specific builds when providing but
-reports and reproduductions.
+project to identify the contents of a specific builds when providing bug
+reports and reproductions.
 
 ## How do I get the early access builds?
 
@@ -46,7 +46,7 @@ redirects:
 
 At the time of writing this will provide you with jdk-21.0.3+3.  If you want
 a previous build to compare with then you can specify a particular version
-directly when calling them API, for example this will retrieve jdk-21.0.3+2
+directly when calling the API, for example this will retrieve jdk-21.0.3+2
 from the previous week:
 
 - https://api.adoptium.net/v3/binary/version/jdk-21.0.3+2-ea-beta/linux/aarch64/jdk/hotspot/normal/adoptium
@@ -99,15 +99,24 @@ to those referenced earlier it can be downloaded from:
 
 ## Why am I not seeing early access builds for the latest release?
 
-There is one caveat for early access builds is that for the few months after
-a new major release comes out when it is typically managed by Oracle there
-are no regular tags produced so we cannot use the processes described in
-this article to build from tags.  In this case we will revert to building
+There is one caveat for producing early access builds using this procedure. 
+The process relies on the party maintaining the upstream version to perform
+the tagging in public.  If those tags aren't visible in public, we have no
+way to build from an invisible tag.  This usually happens for the time
+period when new major JDK versions get released and subsequent quarterly
+security updates for those releases are being handled by Oracle.  For
+example between JDK `22` GA, `22.0.1` and `22.0.2` releases.  There are no
+public tags available for early access tags `jdk-22.0.1+1`, `jdk-22.0.1+2`
+and so on.  Should processes change some time in the future we'd of course
+provide early access builds using the same process as for other releases.
+
+In the case of no publicly visible tags, however, we will revert to building
 regularly from the head of the repository.  In these cases if you need to
-know what is in each version you can determine which github SHA we built
-from using corresponding SBoM that can be downloaded from the API by
+know what is in each version you can determine which git SHA we built from
+using corresponding SBoM artefact that can be downloaded from the API by
 replacing “/jdk/” with “/sbom/” in the above URL.  For example:
 
+
 - https://api.adoptium.net/v3/binary/version/jdk-22+36-ea-beta/linux/aarch64/sbom/hotspot/normal/eclipse?project=jdk
 
 If you are using a GNU grep then this will easily show the commit: