diff --git a/docs/hypernode-deploy/getting-started/configure-ci-cd.md b/docs/hypernode-deploy/getting-started/configure-ci-cd.md
index c36e2b36..75eb7f19 100644
--- a/docs/hypernode-deploy/getting-started/configure-ci-cd.md
+++ b/docs/hypernode-deploy/getting-started/configure-ci-cd.md
@@ -17,8 +17,8 @@ In this example we'll be covering the Github Actions CI/CD configuration.
 
 Hypernode Deploy needs a few 'credentials' to be able to function. The necessary credentials are:
 
-1. The private SSH key. (`SSH_PRIVATE_KEY`)
-1. The composer auth.json file, optional. (`DEPLOY_COMPOSER_AUTH`)
+1. The private SSH key as base64 encoded string. (`SSH_PRIVATE_KEY`)
+1. The composer auth.json file as base64 encoded string, optional. (`DEPLOY_COMPOSER_AUTH`)
    - This is only necessary when your project needs to access private Composer repositories.
 1. The Hypernode API token, optional. (`HYPERNODE_API_TOKEN`)
    - This is only necessary when you make use of Hypernode API driven features like Brancher.