update: updating Cross-platform and native development

mpd.tree

@@ -176,7 +176,7 @@
 	</toc-element>
 	<toc-element toc-title="Multiplatform journal">
 		<toc-element toc-title="Cross-platform mobile development" topic="cross-platform-mobile-development.md"/>
-		<toc-element toc-title="Native and cross-platform mobile development" topic="native-and-cross-platform.md"/>
+		<toc-element toc-title="Native and cross-platform mobile development" topic="native-and-cross-platform.topic"/>
 		<toc-element toc-title="Six popular cross-platform app development frameworks" topic="cross-platform-frameworks.md"/>
 		<toc-element topic="multiplatform-introduce-your-team.md"/>
 		<toc-element toc-title="iOS and Android app development" topic="ios-android-app-development.md"/>

topics/journal/cross-platform-mobile-development.md

@@ -46,7 +46,7 @@ The only similarity between cross-platform and hybrid development is code sharea
 
 ### Native or cross-platform app development: a longstanding debate
 
-[The debate around native and cross-platform development](native-and-cross-platform.md) remains unresolved in the tech community. Both technologies are in constant evolution and come with their own benefits and limitations.
+[The debate around native and cross-platform development](native-and-cross-platform.topic) remains unresolved in the tech community. Both technologies are in constant evolution and come with their own benefits and limitations.
 
 Some experts still prefer native mobile development over multiplatform solutions, identifying the stronger performance and better user experience of native apps as some of the most important benefits.
 

topics/journal/multiplatform-introduce-your-team.md

@@ -26,7 +26,7 @@ At this stage, you need to show that using Kotlin Multiplatform could bring valu
 KMP has been widely used in production since its Alpha release. As a result, JetBrains has been able to collect extensive feedback and provide an even better development experience in the [Stable version](https://blog.jetbrains.com/kotlin/2023/11/kotlin-multiplatform-stable/).
 
 * **Ability to use all iOS and Android features** – Whenever a task cannot be accomplished in the shared code or whenever you want to use specific native features, you can use the [expect/actual](multiplatform-expect-actual.md) pattern to seamlessly write platform-specific code.
-* **Seamless performance** – Shared code written in Kotlin is compiled into different output formats for different targets: Java bytecode for Android and native binaries for iOS. Thus, there is no additional runtime overhead when it comes to executing this code on platforms, and the performance is comparable to [native apps](native-and-cross-platform.md).
+* **Seamless performance** – Shared code written in Kotlin is compiled into different output formats for different targets: Java bytecode for Android and native binaries for iOS. Thus, there is no additional runtime overhead when it comes to executing this code on platforms, and the performance is comparable to [native apps](native-and-cross-platform.topic).
 * **Compatibility with legacy code** – No matter how large your project is, your existing code will not prevent you from integrating Kotlin Multiplatform. You can start writing cross-platform code at any moment and connect it to your iOS and Android apps as a regular dependency, or you can use the code you've already written and modify it to be compatible with iOS.
 
 Being able to explain _how_ a technology works is crucial, as nobody likes it when a discussion seems to rely on magic. People might think the worst if anything is unclear to them, so be careful not to make the mistake of thinking something is too obvious to warrant an explanation. Instead, try to explain all the basic concepts before moving on to the next stage. This document on [multiplatform programming](get-started.topic) could help you systemize your knowledge to prepare for this experience.