wip: clean up

Author: ivanpovazan

docs/core/deploying/native-aot/ios-like-platforms/creating-and-consuming-custom-frameworks.md

@@ -6,7 +6,7 @@ ms.author: ivanpovazan
 ms.date: 11/21/2024
 ---
 
-# Build native libraries for iOS-like platforms
+# Create and consume custom frameworks for iOS-like platforms
 
 Starting from .NET 9, Native AOT supports publishing .NET class libraries that don't depend on iOS workloads for iOS-like platforms.
 This support enables you to create self-contained native libraries that can be consumed from iOS, Mac Catalyst, and tvOS applications.

docs/core/deploying/native-aot/ios-like-platforms/index.md

@@ -8,19 +8,20 @@ ms.date: 11/21/2024
 
 # Native AOT support for iOS-like platforms
 
-Starting from .NET 8, Native AOT supports targeting iOS-like platforms. The term **iOS-like platforms** refers to Apple platforms that use similar APIs such as: iOS, MacCatalyst and tvOS.
+Starting from .NET 8, Native AOT supports targeting iOS-like platforms. The term *iOS-like platforms* refers to Apple platforms that use similar APIs such as: iOS, MacCatalyst and tvOS.
 
 In the first release, the support was experimental, while in .NET 9 these platforms received full support with Native AOT.
 
 Based on the use case, the support can be divided into:
 
-- support for assemblies referencing OS-specific APIs through .NET mobile workloads (like: .NET MAUI apps)
-- support for assemblies without OS-specific API dependencies
+- support for applications and libraries without OS-specific API dependencies
+- support for applications and libraries referencing OS-specific APIs
 
-The former is a more common scenario and is described in detail in [How MAUI supports Native AOT](/dotnet/maui/deployment/nativeaot).
-For the latter use case Native AOT deployment can be achieved by:
+## Support for applications and libraries without OS-specific API dependencies
 
-1. Enable Native AOT deployment by including the following properties in the project file:
+This refers to .NET projects targeting the general or non-OS-specific target framework (like: `net9.0`), for which Native AOT can be enabled in the following way:
+
+1. Include the following properties in your project file:
 
     ```xml
     <PublishAot>true</PublishAot>
@@ -29,16 +30,22 @@ For the latter use case Native AOT deployment can be achieved by:
 
 2. Publish the project for the desired iOS-like target platform by specifying adequate runtime identifier (later referred to as `<rid>`):
 
-- `ios-arm64`, for iOS physical devices
-- `iossimulator-arm64` or `iossimulator-x64`, for iOS simulators
-- `maccatalyst-arm64` or `maccatalyst-x64`, for Mac Catalyst
-- `tvos-arm64`, for tvOS physical devices
-- `tvossimulator-arm64` or `tvossimulator-x64`, for tvOS simulators
+    - `ios-arm64`, for iOS physical devices
+    - `iossimulator-arm64` or `iossimulator-x64`, for iOS simulators
+    - `maccatalyst-arm64` or `maccatalyst-x64`, for Mac Catalyst
+    - `tvos-arm64`, for tvOS physical devices
+    - `tvossimulator-arm64` or `tvossimulator-x64`, for tvOS simulators
 
-and execute the following command:
+    and execute the following command:
 
-```
-dotnet publish -r <rid>
-```
+    ```
+    dotnet publish -r <rid>
+    ```
 
 For specifics of building and consuming native libraries on iOS-like platforms, see [How to create and consume custom frameworks with Native AOT for iOS-like platforms](./creating-and-consuming-custom-frameworks.md).
+
+## Support for applications and libraries referencing OS-specific APIs
+
+This refers to .NET MAUI projects targeting OS-specific target frameworks (like: `net9.0-ios`).
+
+How Native AOT can be enabled for .NET MAUI apps, see [Native AOT deployment on iOS and Mac Catalyst](/dotnet/maui/deployment/nativeaot).