6808 docbug

.github/ISSUE_TEMPLATE/release-issue-template.md

@@ -15,12 +15,13 @@ assignees: ''
 - **Estimnated GA Date:** 
 - 
 ### Notes
-**List any special concerns for this release that are not already tracked in anothere issue, such as release dependencies, Javadoc updates, support level changes, planned docs refresh, etc.**
+**List any special concerns for this release that are not already tracked in another issue, such as release dependencies, Javadoc updates, support level changes, planned docs refresh, etc.**
 
 ### Release checklist
 - [ ] If any Jakarta or MicroProfile API docs are updated with this release, work with development to get the updates merged to the `docs-javadoc` repo (1-2 weeks before GA)
 - [ ] All issues with a label for this release and any other issues included in the release milestone are completed and closed, with content merged to vNext. (~3 working days before GA)
 - [ ] All autogenerated documentation is refreshed on draft (~3 working days before GA)
-- [ ] Confirm with team that docs are frozen and no more updates will be sent to vNext (3 working days before GA).
+- [ ] Confirm with the team that docs are frozen and no more updates will be sent to vNext (3 working days before GA).
+- [ ] Verify main feature epic statuses to ensure that all targeted features will be included in the release (before closing doc feature issues and again 1-2 working days before GA).
 - [ ] [Publish docs to production on GA](https://github.com/OpenLiberty/docs-playbook#publishing-a-new-release-of-open-liberty-docs)
 - [ ] Determine if a docs refresh will be needed before the next upcoming release. If so, make a note of the date and leave this issue open until complete. If not, close this issue. 

modules/reference/pages/config/server-configuration-overview.adoc

@@ -266,7 +266,7 @@ server run myserver -- --variableName=variableValue
 ----
 
 Environment variables can be accessed as variables.
-As of version 19.0.0.3, you can reference the environment variable name directly.
+You can reference the environment variable name directly.
 If the variable cannot be resolved as specified, the `server.xml` file looks for the following variations on the environment variable name:
 
 * Replace all non-alphanumeric characters with the underscore character (`_`)
@@ -278,16 +278,7 @@ For example, if you enter `${my.env.var}` in the `server.xml` file, it looks for
 . my_env_var
 . MY_ENV_VAR
 
-For versions 19.0.0.3 and earlier, you can access environment variables by adding `env.` to the start of the environment variable name, as shown in the following example:
-
-[source,xml]
-----
-<httpEndpoint id="defaultHttpEndpoint"
-              host="${env.HOST}"
-              httpPort="9080" />
-----
-
-Variables can be loaded from files located in directories that are specified by the `VARIABLE_SOURCE_DIRS` environment variable.
+The `VARIABLE_SOURCE_DIRS` environment variable specifies directories from which variables can be loaded.
 If this environment variable is not specified, the default location for the variable directory is `${server.config.dir}/variables`.
 To define a list of directories as the value for this variable, separate each directory with the path separator for your operating system. For Windows, the path separator is a semicolon (`;`). For Unix-based systems, the path separator is a colon (`:`).