diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md
index def34ad0e7f..71684afc779 100644
--- a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md
+++ b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md
@@ -10,7 +10,7 @@ The reason for this is that the KUDU deploy process fails. This process takes th
 
 To resolve this issue, remove the `RestorePackagesWithLockFile` to allow the deployments to go through as expected.
 
-## cloud-sync
+## Cloud Sync
 
 ### The projects left-most mainline environment has changed
 
@@ -76,7 +76,14 @@ Your pipeline should now be functioning as expected.
 
 For GitHub, see the [Skip cloud-sync in GitHub](troubleshooting.md#skip-cloud-sync-in-github) section.
 
-With a few clicks you can manually trigger a pipeline to run without the cloud-sync:
+Navigate to your `azure-release-pipeline.yaml` and comment out these two lines:
+
+```sh
+dependsOn: cloudSyncStage
+condition: in(dependencies.cloudSyncStage.result, 'Succeeded', 'Skipped')
+```
+
+Trigger a code deployment and ensure that you uncheck the "Umbraco Cloud Sync" stage as mentioned below.
 
 1. Ensure that your Azure DevOps repository is up to date with any changes in your Umbraco Cloud environment.
 2. Find the pipeline in Azure DevOps.
diff --git a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md
index 835ff55455b..89e4c3d2852 100644
--- a/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md
+++ b/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/config-transforms.md
@@ -34,6 +34,8 @@ The `{environment}` part needs to be replaced with the target environment, for w
 
 Create this file in your local project clone to ensure it's added to the repository.
 
+{% hint style="info" %} If you don't have a web.config you will need to create one locally as well. {% endhint %}
+
 When the file is deployed to the Live environment, the transforms will be applied to the `Web.config` file in the `Root` of your project. In the case that you have mutliple mainline environments, the `Web.Production.config` will **only** transform the `Web.config` on the Live environment.
 
 For each deployment, the Umbraco Cloud engine searches for all of the `.{environment}.config` files in your site and apply the transforms.
@@ -93,6 +95,8 @@ The snippet requires a `web.config` file with a matching structure; otherwise, t
 
 This config transform will add a `<rule>` to `<system.webServer><rewrite><rules>`. The `xdt:Transform` attribute is used to tell the system what to transform. In this case, the value is `Insert`, which means it will add the section if it's not already in the config file.
 
+If you don't have the `<rewrite>` and `<rules>` section in your `web.config` file, you can add the attribute `xdt:Transform="InsertIfMissing"` to those two sections in the transform file. This ensures they are applied to the `web.config`.
+
 ## appsettings.json transforms
 
 On Umbraco Cloud, projects come with an **appsettings.json** file for each of your different environments.