diff --git a/content/blog/aqavit-graduation-ceremony/index.md b/content/blog/aqavit-graduation-ceremony/index.md
index 4ed60a4fd..0ab85f90c 100644
--- a/content/blog/aqavit-graduation-ceremony/index.md
+++ b/content/blog/aqavit-graduation-ceremony/index.md
@@ -21,7 +21,7 @@ I am not a fan of unnecessary process.  As a project lead of the AQAvit project,
 
 I learned that the release review process was not as onerous as I had expected.  The Eclipse Foundation is streamlining many of the steps, reviewing and removing some of the previously required pieces of documentation that are not necessary for a project to have in order to prove it is healthy and mature.  Some of the required documentation includes the License, Readme and Contributing files as well as recommended Code of Conduct and Security files be present in every repository within a given Eclipse project.  The AQAvit project which happens to hierarchically be a sub-project of Eclipse Adoptium, has its [7 repositories](https://projects.eclipse.org/projects/adoptium.aqavit/developer) under the Adoptium Github organization, so many of those required files are inherited from the Github organization files.  For the [AQAvit 1.0.0 release review](https://gitlab.eclipse.org/eclipsefdn/emo-team/emo/-/issues/669), there were very few updates needed.   
 
-Having the Eclipse release process look at the metadata and legal aspects of a project means that project leads and committers can focus on the day to day technical work and innovation.  The AQAvit project typically coordinates its Github releases to be available a few weeks ahead of the [JDK release schedule](https://www.java.com/releases) as the many vendors who distribute binaries built from source code originally sourced from the [OpenJDK project](https://openjdk.org/), use AQAvit to verify the quality of the binaries they are producing and distributing.
+Having the Eclipse release process look at the metadata and legal aspects of a project means that project leads and committers can focus on the day to day technical work and innovation.  The AQAvit project typically coordinates its Github releases to be available a few weeks ahead of the [JDK release schedule](https://www.java.com/releases) as the many vendors who distribute binaries built from source code originally sourced from the [OpenJDK project](https://openjdk.org/), use AQAvit to verify the quality of the binaries they are producing and distributing.  Because of this, AQAvit produces multiple releases per year in step with the JDK release schedule.  The complementary Eclipse release process for a project only needs to happen once a year as the areas of focus it is concerned with do not change rapidly.
 
 ## The Scope of AQAvit