Clean up

Author: ivanpovazan

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

@@ -30,9 +30,7 @@ After publishing, Native AOT applications are true native binaries. The managed
 
 ### Debugging .NET MAUI iOS applications with NativeAOT
 
-.NET MAUI iOS applications which are compatible with NativeAOT and are properly configured and published with this deployment model (for more information see: [Publish using Native AOT](https://learn.microsoft.com/dotnet/maui/deployment/nativeaot?view=net-maui-9.0#publish-using-native-aot), can be debugged in the following ways.
-
-#### iOS
+.NET MAUI iOS applications which are compatible with NativeAOT and are properly configured and published with this deployment model (for more information see: [Publish using Native AOT](https://learn.microsoft.com/dotnet/maui/deployment/nativeaot?view=net-maui-9.0#publish-using-native-aot), can be debugged in the following way (tested with `Xcode 16.0` CLI tools):
 
 1. Publish your app with Native AOT targeting `ios-arm64` and store the following information:
 
@@ -73,7 +71,7 @@ By default, debug symbols are stripped from the application's binary file into *
 
 ## CPU profiling
 
-[Xcode Instruments](https://developer.apple.com/download/) can be used to collect CPU samples of a Native AOT application.
+[Xcode Instruments](https://developer.apple.com/xcode) can be used to collect CPU samples of a Native AOT application.
 
 ## Heap analysis