zowe · Martin-Zeithaml · Jul 10, 2025 · Jul 10, 2025 · Jul 10, 2025 · Jul 11, 2025
diff --git a/.github/workflows/link-checker.yml b/.github/workflows/link-checker.yml
@@ -26,16 +26,24 @@ jobs:
           done
 
       - name: Restore lychee cache
-        uses: actions/cache@v4
+        id: lychee-cache-restore
+        uses: actions/cache/restore@v4
         with:
           path: .lycheecache
-          key: cache-lychee-${{ github.base_ref || github.ref_name }}
+          key: cache-lychee-${{ github.event.pull_request.head.ref || github.base_ref || github.ref_name }}
           restore-keys: cache-lychee-
-          save-always: true
 
       - name: Run lychee
         uses: lycheeverse/lychee-action@v1
         with:
           args: "--accept 403,406,429 --cache --include-fragments --max-cache-age 1d --max-concurrency 2 --no-progress --timeout 60 --verbose 'docs/**/*.md'"
           fail: true
           token: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Always save lychee cache
+        id: save-lychee-cache
+        if: always()
+        uses: actions/cache/save@v4
+        with:
+            key: ${{ steps.lychee-cache-restore.outputs.cache-primary-key }}
+            path: .lycheecache
diff --git a/docs/images/zosmf/inputvars-jcl-enable.png b/docs/images/zosmf/inputvars-jcl-enable.png
diff --git a/docs/user-guide/cli-authentication-methods.md b/docs/user-guide/cli-authentication-methods.md
@@ -14,7 +14,7 @@ If you configure multiple authentication methods for a specific service, set the
 
 ## Order of precedence
 
-You can configure the order that Zowe CLI follows to search for an available authentication method, or you can leave the [default order of precedence](../extend/extend-cli/cli-authentication-mechanisms.md#default-order-of-precendence) used by the service you are connecting to.
+You can configure the order that Zowe CLI follows to search for an available authentication method, or you can leave the [default order of precedence](../extend/extend-cli/cli-authentication-mechanisms.md#default-order-of-precedence) used by the service you are connecting to.
 
 To configure a different order of precedence, add the `authOrder` property to the profile for the service to which you want to connect.:
 

diff --git a/docs/user-guide/configure-apiml-zosmf-workflow.md b/docs/user-guide/configure-apiml-zosmf-workflow.md
@@ -14,6 +14,10 @@ Ensure that you meet the following requirements before you start your Zowe confi
 - Install and configure z/OSMF
 - Install Zowe with an SMP/E build, PSWI, or a convenience build
 
+:::note
+From Zowe 3.3.0 forward, the Zowe z/OSMF Workflow supports JCL-driven configuration. This will become the default method of configuration in a future release. Read [this guide](./configuring-zowe-via-jcl.md#following-existing-zosmf-workflow-documentation) for more information.
+:::
+
 ## Overview of Stand-alone Zowe API ML Configuration workflow
 
 The following components are automatically enabled after performing the **Stand-alone Zowe API ML Configuration** workflow:

diff --git a/docs/user-guide/configure-zowe-runtime.md b/docs/user-guide/configure-zowe-runtime.md
@@ -7,7 +7,7 @@ Begin configuration of your installation of Zowe z/OS components by initializing
 
 Use one of the following options to initialize Zowe z/OS runtime:
 
-* Initialize Zowe maunually using zwe init command group
+* Initialize Zowe manually using zwe init command group
 * Configure Zowe with z/OSMF workflows
 
 ## Initialize Zowe manually using zwe init command group
@@ -18,7 +18,7 @@ After your installation of Zowe runtime, you can run the `zwe init` command to p
 * Create user IDs and security manager settings (Security Admin)
 * Provide APF authorize load libraries (Security Admin)
 * Configure Zowe to use TLS certificates (Security Admin)
-* Configure VSAM files to run the Zowe caching service used for high availability (HA)
+* Configure the Zowe caching service for high availability (HA)
 * Configure the system to launch the Zowe started task
 
 For more information about this z/OS runtime initialization method, see [Configuring Zowe with zwe init](./initialize-zos-system.md)

diff --git a/docs/user-guide/configure-zowe-zosmf-workflow.md b/docs/user-guide/configure-zowe-zosmf-workflow.md
@@ -15,6 +15,10 @@ Ensure that you meet the following requirements before you start your Zowe confi
 - Install and configure z/OSMF
 - Install Zowe with an SMP/E build, PSWI, or a convenience build
 
+:::note
+From Zowe 3.3.0 forward, the Zowe z/OSMF Workflow supports JCL-driven actions. This will become the default method of configuration in a future release. Read [this guide](./configuring-zowe-via-jcl.md#following-existing-zosmf-workflow-documentation) for more information.
+:::
+
 ## Overview of Full Zowe server-side configuration for Zowe 3.0 workflow
 
 You can complete the following tasks with the **Full Zowe server-side configuration for Zowe 3.0** workflow:

diff --git a/docs/user-guide/configuring-overview.md b/docs/user-guide/configuring-overview.md
@@ -18,17 +18,21 @@ Successful completion of steps 2, 3, and 4 may require elevated security permiss
 
 ## Configuring Zowe runtime
 
-To cofigure Zowe runtime, choose from the following options:
+To configure Zowe runtime, choose from the following options:
 
-* **Option 1: Configure Zowe manually using the `zwe init` command group**  
-To run the `zwe init` command, it is necessary to create a Zowe configuration file. For more information about this file, see the [Runtime directory](./installandconfig.md#runtime-directory) which details all of the started tasks in the article _Preparing for installation_.
+* **Option 1: Configure Zowe using the `zwe init` command group**  
+To run the `zwe init` command, it is necessary to create a Zowe configuration file. For more information about this file, see the [Zowe configuration file](./installandconfig.md#zowe-configuration-file-zoweyaml).
 
     Once your configuration file is prepared, see [Configuring Zowe with zwe init](./initialize-zos-system.md), for more information about using the `zwe init` command group.
 
-* **Option 2: Configure Zowe via JCL**
+:::note
+From Zowe 3.3.0 forward, the `zwe init` command supports JCL-driven actions. This will become the default method of `zwe init` configuration in a future release. Read [this guide](./configuring-zowe-via-jcl.md) to get started.
+:::
+
+* **Option 2: Configure Zowe via manual JCL**
 You can configure Zowe by directly customizing JCLs. The Zowe Runtime Dataset `SZWESAMP` contains JCL samples that have templates referencing `zowe.yaml` parameters. These samples should not be submitted without modification.
 
-    For more information, see [Configuring Zowe via JCL](./configuring-zowe-via-jcl.md)
+    For more information, see [Configuring Zowe via JCL](./configuring-zowe-via-jcl.md#getting-started-with-manual-jcl-submission)
 
 * **Option 3: Configure Zowe with z/OSMF workflows**  
 You can execute the Zowe configuration workflow either from a PSWI during deployment, or later from a created software instance in z/OSMF. Alternatively, you can execute the configuration workflow z/OSMF during the workflow registration process.
@@ -43,7 +47,7 @@ You can execute the Zowe configuration workflow either from a PSWI during deploy
 Configuration of the z/OS system is dependent on the specific Zowe features and functionalities you would like to employ with your Zowe installation. 
 
 :::tip
-Note that configuring the z/OS system requires elevated permissions. We recommend you consult with your security administrator to perform the reqired steps to configure the z/OS system.
+Note that configuring the z/OS system requires elevated permissions. We recommend you consult with your security administrator to perform the required steps to configure the z/OS system.
 :::
 
 For more information, see [Configuring the z/OS system for Zowe](./configure-zos-system.md).