diff --git a/_snippets/source-control-environments/multi-instance-multi-branch-pros-cons.md b/_snippets/source-control-environments/multi-instance-multi-branch-pros-cons.md
index 21aa391a1..b1ce86a2f 100644
--- a/_snippets/source-control-environments/multi-instance-multi-branch-pros-cons.md
+++ b/_snippets/source-control-environments/multi-instance-multi-branch-pros-cons.md
@@ -3,5 +3,5 @@ The advantages of this pattern are:
 * An added safety layer to prevent changes getting into your production environment by mistake. You have to do a pull request in GitHub to copy work between environments.
 * It supports more than two instances.
 
-The disadvantages is more manual steps to copy work between environments.
+The disadvantage is more manual steps to copy work between environments.
 
diff --git a/docs/_images/source-control-environments/vc-multi-one.png b/docs/_images/source-control-environments/vc-multi-one.png
index 2a6351d83..a2abf427f 100644
Binary files a/docs/_images/source-control-environments/vc-multi-one.png and b/docs/_images/source-control-environments/vc-multi-one.png differ
diff --git a/docs/source-control-environments/using/manage-variables.md b/docs/source-control-environments/using/manage-variables.md
index 84ffe3255..5225686f8 100644
--- a/docs/source-control-environments/using/manage-variables.md
+++ b/docs/source-control-environments/using/manage-variables.md
@@ -1,16 +1,11 @@
 ---
-title: Credential and variable values
+title: Manage variables
 description: Manage variable values in n8n using the API and source control.
 ---
 
 # Manage variables
 
-n8n doesn't sync credential and variable values with Git. You must set up the credentials manually when setting up a new instance. You can choose to set up variables manually, or [using the API](#manage-variables-using-the-api).
-
-[TODO: cut mention of creds here]
-
-!!! note "Coming soon: credential support with secret managers"
-	n8n is working on support for external secret managers to handle credentials. Once this feature is complete, n8n will support linking the secret manager to multiple instances.
+n8n doesn't sync variable values with Git. You must set up the credentials manually when setting up a new instance. You can choose to set up variables manually, or [using the API](#manage-variables-using-the-api).
 
 ## Manage variables using the API
 
diff --git a/docs/source-control-environments/using/push-pull.md b/docs/source-control-environments/using/push-pull.md
index e67255dd4..1d1504a92 100644
--- a/docs/source-control-environments/using/push-pull.md
+++ b/docs/source-control-environments/using/push-pull.md
@@ -36,4 +36,13 @@ When you pull from Git to an n8n instance, the workflow owner may change. If the
 
 ## What gets committed
 
+n8n commits the following to Git:
+
+* Workflows, including their tags and the email address of the workflow owner. You can choose which workflows to push.
+* Credential stubs (ID, name, type)
+* Variable stubs (ID and name)
+
 You can programmatically [Manage variables](/source-control-environments/using/manage-variables/) using the n8n API.
+
+!!! note "Coming soon: credential support with secret managers"
+	n8n is working on support for external secret managers to handle credentials. Once this feature is complete, n8n will support linking the secret manager to multiple instances.