diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index d6dd79daa..53a703910 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -12,7 +12,10 @@ jobs:
       # parse the release version from the github ref
       # https://stackoverflow.com/questions/58177786/get-the-current-pushed-tag-in-github-actions
       - name: Set env
-        run: echo "RELEASE_VERSION=${GITHUB_REF#refs/*/}" >> $GITHUB_ENV
+        run: |
+          echo "RELEASE_VERSION=${GITHUB_REF#refs/*/}" >> $GITHUB_ENV
+          echo "$HOME/.local/bin/" >> $GITHUB_PATH
+
       - name: show release version
         run: echo ${{ env.RELEASE_VERSION }}
       
@@ -27,7 +30,9 @@ jobs:
 
       # this setup is all for the github pages deployment to work
       - name: install sphinx
-        run: pip3 install --user sphinx sphinx_rtd_theme
+        run: |
+          pip3 install --user sphinx sphinx_rtd_theme
+          which sphinx-build
 
       - name: setup git
         run: |
diff --git a/src/sphinx/archetypes/java_app/customize.rst b/src/sphinx/archetypes/java_app/customize.rst
index 9323a4e40..e8b40cd11 100644
--- a/src/sphinx/archetypes/java_app/customize.rst
+++ b/src/sphinx/archetypes/java_app/customize.rst
@@ -30,7 +30,7 @@ configuration file during execution. You can define the configuration file locat
 
 
 The configuration path is the path on the **target** system. This means that native-packager needs to process this path
-to create a valid ``universal:mapping``s entry.
+to create a valid ``universal:mapping`` s entry.
 
 * ``${app_home}/../`` is removed
 * ``%APP_HOME%`` is removed and ``\`` is being replaced with ``/``
diff --git a/src/sphinx/archetypes/java_server/customize.rst b/src/sphinx/archetypes/java_server/customize.rst
index 7f1748bae..28172ef57 100644
--- a/src/sphinx/archetypes/java_server/customize.rst
+++ b/src/sphinx/archetypes/java_server/customize.rst
@@ -4,7 +4,7 @@
 Application Configuration
 =========================
 
-After :doc:`creating a package <my-first-project>`, the very next thing needed, usually, is the ability for users/ops to customize the application once it's deployed.   Let's add some configuration to the newly deployed application.
+After :doc:`creating a package <java_app/index.rst>`, the very next thing needed, usually, is the ability for users/ops to customize the application once it's deployed.   Let's add some configuration to the newly deployed application.
 
 There are generally two types of configurations:
 
diff --git a/src/sphinx/formats/graalvm-native-image.rst b/src/sphinx/formats/graalvm-native-image.rst
index 48cf9c166..90e9b8dd2 100644
--- a/src/sphinx/formats/graalvm-native-image.rst
+++ b/src/sphinx/formats/graalvm-native-image.rst
@@ -1,7 +1,7 @@
 .. _graalvm-native-image-plugin:
 
 GraalVM Native Image Plugin
-=============
+===========================
 
 GraalVM's ``native-image`` compiles Java programs AOT (ahead-of-time) into native binaries.
 
@@ -48,7 +48,7 @@ Settings
 --------
 
 ``native-image`` Executable Command (Pay attention if you are using Windows OS)
-~~~~
+
 Putting ``native-image`` in ``PATH`` does not work for Windows. ``native-image`` is a batch file in Windows that calls another executable to compile the Java classes to a standalone executable. Therefore, the full path to the batch file e.g. ``C:\Program Files\Java\graalvm\bin\native-image.cmd`` must be provided. It is important to include ``.cmd``.
 
   ``graalVMNativeImageCommand``