Remove unreleated changes

docs/content/developer/getting-started/first-app/build-test.mdx

@@ -238,7 +238,7 @@ Transaction effects, such as object creation and transfer become visible only af
 
 :::
 
-The final owner executes the fourth and final transaction that retrieves the `sword` object from storage and checks if it has the expected properties. Remember, as described in [Testing a package](#testing-a-package-testing-a-package), in the pure Move testing scenario, after an object is available in Move code (after creation or retrieval from emulated storage), it cannot simply disappear.
+The final owner executes the fourth and final transaction that retrieves the `sword` object from storage and checks if it has the expected properties. Remember, as described in [Testing a package](#testing-a-package), in the pure Move testing scenario, after an object is available in Move code (after creation or retrieval from emulated storage), it cannot simply disappear.
 
 In the pure Move testing function, the function transfers the `sword` object to the fake address to handle the disappearing problem. The `test_scenario` package provides a more elegant solution, however, which is closer to what happens when Move code actually executes in the context of IOTA - the package simply returns the `sword` to the object pool using the `test_scenario::return_to_sender` function. For scenarios where returning to the sender is not desirable or if you would like to simply destroy the object, the `test_utils` module also provides the generic `destroy<T>` function, that can be used on any type `T` regardless of its ability. It is advisable to check out other useful functions in the [`test_scenario`](https://github.com/iotaledger/iota/blob/main/crates/iota-framework/packages/iota-framework/sources/test/test_scenario.move) and [`test_utils`](https://github.com/iotaledger/iota/blob/main/crates/iota-framework/packages/iota-framework/sources/test/test_utils.move) modules as well.
 

docs/content/developer/iota-101/iota-move-concepts/packages/custom-policies.mdx

@@ -8,7 +8,7 @@ Protecting the ability to upgrade a package on chain using a single key can pose
 
 <UpgradeSingleKeyRisk />
 
-To address the security risk of single-key upgrade ownership poses while still providing the opportunity to [upgrade live packages](upgrade.mdx), IOTA offers _custom upgrade policies_. These policies protect `UpgradeCap` access and issue `UpgradeTicket` objects that authorize upgrades on a case-by-case basis.
+To address the security risk of single-key upgrade ownership poses while still providing the opportunity to [upgrade live packages](./upgrade.mdx), IOTA offers _custom upgrade policies_. These policies protect `UpgradeCap` access and issue `UpgradeTicket` objects that authorize upgrades on a case-by-case basis.
 
 ## Compatibility {#compatibility}
 

docs/content/developer/standards/kiosk-apps.mdx

@@ -8,7 +8,7 @@ Kiosk apps are a way to extend the functionality of IOTA Kiosk while keeping the
 There are two types of apps:
 
 - [Basic apps](#basic-apps)
-- [Permissioned apps](#permissioned-apps-using-the-kiosk-apps-api-permissioned-apps)
+- [Permissioned apps](#permissioned-apps)
 
 ## Basic apps
 

docs/content/sidebars/developer.js

@@ -726,7 +726,8 @@ const developer = [
         type: 'category',
         label: 'Exchange integration',
         items: ['developer/exchange-integration/exchange-integration'],
-    },{
+    },
+    {
         type: 'category',
         label: 'Decentralized Identity',
         link: {
@@ -804,35 +805,6 @@ const developer = [
             'developer/iota-identity/faq',
         ],
     },
-    {
-        type: 'category',
-        label: 'Integrate Your Exchange',
-        items: [
-            'developer/exchange-integration/exchange-integration',
-
-            {
-                type: 'category',
-                label: 'Migrating IOTA/Shimmer Stardust',
-                link: {
-                    type: 'doc',
-                    id: 'developer/stardust/stardust-migration',
-                },
-                items: [
-                    'developer/stardust/exchanges',
-                    'developer/stardust/move-models',
-                    'developer/stardust/addresses',
-                    'developer/stardust/units',
-                    'developer/stardust/migration-process',
-                    'developer/stardust/claiming',
-                    'developer/stardust/vested',
-                    'developer/stardust/testing',
-                    'developer/stardust/if-tools',
-                    'developer/stardust/faq',
-                    'developer/stardust/advanced',
-                ],
-            },
-        ],
-    },
     'developer/dev-cheat-sheet',
 ];
 module.exports = developer;