adds an example of how to generate the value you actually have to put…

… into dockerconfigjson

README.md

@@ -16,7 +16,18 @@ global:
   imagePullSecrets:
     - registry
   secret:
-    dockerconfigjson: "BASE64_ENCODED_JSON_CONTAINING_TOKEN"
+    dockerconfigjson: "BASE64_ENCODED_JSON_CONTAINING_DOCKER_AUTH_CONFIG"
+```
+
+You can generate this value with a bash command like this
+```bash
+echo '{
+        "auths": {
+                "ghcr.io": {
+                        "auth": "TO_BE_REPLACED"
+                }
+        }
+}' | sed "s/TO_BE_REPLACED/$(echo "username:token" | base64 -w 0 )/g" | base64 -w 0
 ```
 
 * Install Verdict-as-a-Service:
@@ -172,7 +183,7 @@ In addition, Sentry will always behave as follows:
 <!-- tag::OtherValues[] -->
 
 | Parameter                                 | Description                                                                                           | Value                          |
-|-------------------------------------------|-------------------------------------------------------------------------------------------------------|--------------------------------|
+| ----------------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------ |
 | global.imagePullSecrets                   | List of image pull secrets                                                                            | - name: registry               |
 | global.secret.dockerconfigjson            | Docker authentication configuration                                                                   | ""                             |
 | cloud.hashLookup.enabled                  | Enable/Disable the cloud hash lookup                                                                  | true                           |