Fixed broken links and images in Umbraco Cloud

umbraco-cloud/deployment/restoring-content/partial-restore.md

@@ -31,7 +31,7 @@ To partially restore the parts you need:
 8. Click **Restore**.
 9. Right-click the Content tree and select **Reload** once the restore is complete.
 
-![Partial restore on empty environment](<../../../umbraco-deploy/deployment-workflow/restoring-content/images/partialRestore-onEmpty (1) (1) (1) (1).gif>)
+![Partial restore on empty environment](images/partialRestore-onEmpty.gif)
 
 Partial Restores on empty environments are helpful when not all content or media is necessary for the tasks to be performed on the new environment. Instead of having to restore everything, doing a partial restore can be used to only restore the parts you need. This will ensure that you can quickly get on your way with the task at hand.
 
@@ -47,7 +47,7 @@ It is possible to use the Partial Restore feature in environments where you alre
 6. Click **Restore**.
 7. Right-click the Content tree and select **Reload** once the restore is complete.
 
-![Partial restore](../../../umbraco-deploy/deployment-workflow/restoring-content/images/partialRestore-onEnvWithContent.png)
+![Partial restore](images/partialRestore-onEnvWithContent.png)
 
 {% embed url="https://www.youtube.com/embed/C5SnrEf78bQ?rel=0" %}
 A video showing how to use partial restores between Umbraco Cloud environments.

umbraco-cloud/product-upgrades/manual-upgrades/manual-upgrade-deploy.md

@@ -52,23 +52,23 @@ Make sure that everything works on the local clone and that you can **run the pr
 <summary>If you are on Umbraco 7 or Umbraco 8, follow these steps to manually upgrade Umbraco Deploy to a later version of your project</summary>
 
 1. Download **Storage Explorer** here: [https://azure.microsoft.com/en-us/products/storage/storage-explorer](https://azure.microsoft.com/en-us/products/storage/storage-explorer) and install it.
-2. Click the **"Plug"** Button (Open Connect Dialog):\
+2. Click the **"Plug"** Button (Open Connect Dialog):
    \
    ![Click the "Plug" Button (Open Connect Dialog)](<../../.gitbook/assets/image (1) (1) (1) (1) (1) (1).png>)
 
 <!---->
 
-3. Choose **"Blob container or directory"**:\
+3. Choose **"Blob container or directory"**:
    ![](<../../.gitbook/assets/image (1) (1) (1) (1) (1) (1) (1).png>)
 
 <!---->
 
-4. Choose **"Anonymously"** when prompted on how you will connect to the blob container.\
+4. Choose **"Anonymously"** when prompted on how you will connect to the blob container.
    ![](<../../.gitbook/assets/image (2) (1) (1) (1) (1) (1).png>)
 
 <!---->
 
-5. Enter [`https://umbraconightlies.blob.core.windows.net/umbraco-deploy-release`](https://umbraconightlies.blob.core.windows.net/umbraco-deploy-release) in the **"Blob container or directory URL":**\\
+5. Enter `https://umbraconightlies.blob.core.windows.net/umbraco-deploy-release` in the **Blob container or directory URL.**
 
 <img src="../../.gitbook/assets/image (3) (1) (1) (1) (1).png" alt="" data-size="original">
 

umbraco-cloud/release-notes/overview-2024/september-2024.md

@@ -18,8 +18,6 @@ For more information about the Secrets Management feature see the [Secrets Manag
 
 We have enhanced the user experience for automatic upgrades in Umbraco Cloud by introducing real-time progress tracking directly in the UI. Now, when an upgrade is in progress, users will be able to see its status and follow along. This provides greater transparency and keeps you informed about the process at every step. No more guessing or waiting in the dark—stay updated as your project moves to the latest version.
 
-<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeHLyuC5E6SuYDPF3HZh33E7DHKNlX4Zrj3jknEPCA-76eFKQuSOwWHMqBeRTSRLzFB3FA2jFNz6Kz0cM683dY7os4tjMZvtB4DM8rxaoKjCfvSAPIC70JXNcjhaTcPPmXNgF7EpdTkLwUpE4XjrE3gOZJh?key=SlsmlhRYGNANsP-KfBECSQ" alt=""><figcaption></figcaption></figure>
-
 ## Improved feedback on deployment errors
 
 When doing deployments between environments in the Cloud Portal, we will now surface all the available logs we have, upon failure. This means all the technical details we can collect, should help in the debugging process.&#x20;

umbraco-cloud/set-up/power-tools/generating-uda-files.md

@@ -119,7 +119,7 @@ Follow these steps to generate UDA files:
 4. Type the following command in the CMD console: `echo > deploy-export`
 5. The Deploy engine will generate UDA files for all the types in your project.
 6. When it's done, you'll end up with a `deploy-complete` marker.
-7. Run an extraction, making sure you can get a `deploy-complete` marker - see [**Run an extraction**](../../deployment/deploy-operations/extract-schema-to-data-files.md) article.
+7. Run an extraction, making sure you can get a `deploy-complete` marker - see [**Run an extraction**](../../set-up/power-tools/manual-extractions.md) article.
 
 Generating UDA files manually might sometimes end up giving you collision errors on your environments due to duplicates. This can be resolved by following our [Structure Error](../../troubleshooting/deployments/structure-error.md) documentation.
 

umbraco-cloud/set-up/project-settings/umbraco-cicd/UmbracoCloudApi.md

@@ -8,7 +8,7 @@ For the scope of this discussion, we will concentrate solely on the endpoints as
 
 ## Getting started
 
-To integrate Umbraco Cloud into your CI/CD pipeline, you'll need to make API calls to the following endpoint [`https://api.cloud.umbraco.com`](https://api.cloud.umbraco.com):
+To integrate Umbraco Cloud into your CI/CD pipeline, you'll need to make API calls to the following endpoint `https://api.cloud.umbraco.com`:
 
 * `/$projectId/deployments`
 * `/$projectId/deployments/$deploymentId`

umbraco-cloud/troubleshooting/deployments/changes-not-being-applied.md

@@ -59,7 +59,7 @@ An example of a faulty config transform not being applied could look something l
 
 1. Verify the Config Transform file mentioned in the error message and ensure the XML is valid.
 2. Update the Config Transform file as necessary on your local solution and deploy the change to the Cloud environments.
-3. Run a ['Schema Deployment From Data Files'](../../deployment/deploy-operations/extract-schema-to-data-files.md) to extract the schema that you previously deployed.
+3. Run a [Schema Deployment From Data File](../../deployment/deploy-dashboard.md#deploy-operations) to extract the schema that you previously deployed.
 
 {% hint style="info" %}
 To find errors in the config transform, you can use an xml validation tool like https://www.xmlvalidation.com/