MOre updates following review

Signed-off-by: Stewart X Addison <sxa@redhat.com>

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

@@ -99,16 +99,17 @@ using similar queries 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 producing early access builds using this procedure.
+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.
+security updates for those releases are being handled (usually 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