fix: secret and variable names in table

Co-authored-by: Mark Goddard <mark@stackhpc.com>

Author: jackhodgkiss

doc/source/configuration/ci-cd.rst

@@ -143,11 +143,11 @@ Workflow Deployment
 +-----------------------------------+----------------------------------------------+
 | KAYOBE_AUTOMATION_SSH_PRIVATE_KEY | <ENV_NAME>_KAYOBE_AUTOMATION_SSH_PRIVATE_KEY |
 +-----------------------------------+----------------------------------------------+
-|       KAYOBE_VAULT_PASSWORD       |  <ENV_NAME>_PRODUCTION_KAYOBE_VAULT_PASSWORD |
+|       KAYOBE_VAULT_PASSWORD       |  <ENV_NAME>_KAYOBE_VAULT_PASSWORD |
 +-----------------------------------+----------------------------------------------+
 |         REGISTRY_PASSWORD         |         <ENV_NAME>_REGISTRY_PASSWORD         |
 +-----------------------------------+----------------------------------------------+
-|           TEMPEST_OPENRC          |     <ENV_NAME>_PRODUCTION_TEMPEST_OPENRC     |
+|           TEMPEST_OPENRC          |     <ENV_NAME>_TEMPEST_OPENRC     |
 +-----------------------------------+----------------------------------------------+
 
     +----------------------------------------------+
@@ -157,7 +157,7 @@ Workflow Deployment
     +--------------------+-------------------------+
     |    REGISTRY_URL    | <ENV_NAME>_REGISTRY_URL |
     +--------------------+-------------------------+
-    |  REGISTRY_USERNAME |    <ENV_NAME>_USERNAME  |
+    |  REGISTRY_USERNAME |    <ENV_NAME>_REGISTRY_USERNAME  |
     +--------------------+-------------------------+
 
 Note the above tables shows the secrets and variables one may need to add to GitHub for a successful deployment.