fix broken links in docs

Author: matas-bitbybit-dev

docs/start/getting-started/basics/assets/cloud/using-textures.mdx

@@ -16,7 +16,7 @@ This tutorial demonstrates how to use image-based cloud assets to create texture
 
 :::info Prerequisites
 *   Ensure you are signed up and logged into the Bitbybit platform. You can [sign up here](https://bitbybit.dev/auth/sign-up).
-*   You should have completed the [Uploading Cloud Assets](/start/general/uploading-cloud-assets) tutorial.
+*   You should have completed the [Uploading Cloud Assets](/start/getting-started/basics/assets/cloud/uploading) tutorial.
 :::
 
 **Sample Image for this Tutorial:**

docs/start/getting-started/basics/assets/local/gltf.mdx

@@ -27,7 +27,7 @@ If you have your own `.glb` or `.gltf` file, you can use that as well.
 ## 1. Uploading the Asset to Local Storage
 
 Before you can use the `BoomBox.glb` (or your own glTF file) in the editors, you need to upload it to your browser's local storage using Bitbybit's local asset manager.
-*   Please follow the steps outlined in our [Uploading Local Assets guide](/start/general/uploading-local-assets).
+*   Please follow the steps outlined in our [Uploading Local Assets guide](/start/getting-started/basics/assets/local/uploading).
 *   When prompted for an asset name during the upload, use "**BoomBox**" (or a name of your choice if using your own file, but remember it for later steps).
 
 Once the asset is uploaded, you can proceed to use it in any of the editors.

docs/start/getting-started/basics/assets/local/intro.mdx

@@ -16,7 +16,7 @@ If you prefer not to use our cloud services for storing your assets, or if you w
 
 *   **Browser-Specific:** Local assets are stored within the specific browser you used to upload them. They are **not** shared across different browsers (e.g., Chrome vs. Firefox) or different devices.
 *   **Sharing Limitations:**
-    *   If your script relies on local assets and you [export the script to a file](/start/general/save-script-to-file) to share with others, those users will **not** automatically have the asset. You would need to provide them with the asset file separately, and they would have to upload it as a local asset in their own browser.
+    *   If your script relies on local assets and you [export the script to a file](/start/getting-started/basics/scripts/save-to-file) to share with others, those users will **not** automatically have the asset. You would need to provide them with the asset file separately, and they would have to upload it as a local asset in their own browser.
 *   **Persistence (Within the Same Browser):** Local assets generally persist within your browser even after you close and reopen the browser window. However, clearing your browser's cache or site data could potentially remove them.
 *   **No Account Needed:** You can use the local asset feature without needing a Bitbybit account.
 

docs/start/getting-started/basics/projects/publish.md

@@ -45,7 +45,7 @@ When you're working in one of our editors (TypeScript, Blockly, or Rete) and fee
 
 3.  **Choose Visibility Options & Publish:**
     A "Publish Project" dialog will open. Here, you'll be presented with several **Visibility options** for your project.
-    *   You can learn more about these options in detail on our [Projects Overview page](start/getting-started/basics/projects/intro).
+    *   You can learn more about these options in detail on our [Projects Overview page](/start/getting-started/basics/projects/intro).
 
     The dialog will look something like this:
 

docs/start/getting-started/basics/scripts/auto-save.md

@@ -16,7 +16,7 @@ The auto save feature in Bitbybit is designed to help protect your work by perio
 *   **You must be signed up and logged into the Bitbybit platform.**
 *   You must be working on a **Script that is part of a Project** you have created.
 
-Only when these conditions are met does our system have a specific entity in our database to associate your work with and update automatically. If you are working on a [local, unsaved script](/start/general/create-script#how-to-create-a-new-local-script-unsaved), you **must manually save your work to a file** if you wish to preserve it.
+Only when these conditions are met does our system have a specific entity in our database to associate your work with and update automatically. If you are working on a [local, unsaved script](/start/getting-started/basics/scripts/auto-save), you **must manually save your work to a file** if you wish to preserve it.
 
 ## IMPORTANT: Auto Save Does NOT Record Version History