Update README.md formatting and instructions.

The product is ".NET for Android", not ".net Android".

The `dotnetcli` code block is for `dotnet …` commands, not just any shell command.

Author: jonpryor

samples/NativeAOT/README.md

@@ -1,12 +1,12 @@
 # NativeAOT Sample
 
-This is the sample for using NativeAOT with .net Android
+This is the sample for using NativeAOT with .NET for Android.
 
 ## Debugging
 
 In order to debug we need to use `lldb`. First install the application
 
-```dotnetcli
+```sh
 ./dotnet-local.sh build samples/NativeAOT/NativeAOT.csproj -c Release -p:DebugSymbols=true -t:Install
 ```
 
@@ -19,7 +19,7 @@ In order to lldb debugging to work we need to make sure we install the `lldb-ser
 The following steps, install the `lldb-server`, stop any existing lldb-server process and they launches
 it. It also sets up the required port forwarding so we can connect to the server from the local machine.
 
-```dotnetcli
+```shell
 adb push $(ANDROID_NDK_HOME)/toolchains/llvm/prebuilt/darwin-x86_64/lib/clang/18/lib/linux/aarch64/lldb-server /data/local/tmp/lldb-server
 adb shell run-as net.dot.hellonativeaot cp /data/local/tmp/lldb-server .
 adb forward tcp:5039 tcp:5039
@@ -31,7 +31,7 @@ Note: We have to run the `lldb-server` in the context of the app so it has the c
 
 Once `lldb-server` is up and running, you will want to run up the app using the following
 
-```dotnetcli
+```shell
 adb shell am start -S --user "0" -a "android.intent.action.MAIN" -c "android.intent.category.LAUNCHER" -n "net.dot.hellonativeaot/my.MainActivity" -D
 ```
 
@@ -41,7 +41,7 @@ If you do not want to the app to pause on startup, you can omit the `-D` argumen
 Now that the app is running we need to get the process id. We do that using `adb shell ps`. 
 The `grep` is used to filter the results to only our app.
 
-```dotnetcli
+```shell
 adb shell ps | grep net.dot.hellonativeaot
 ```
 
@@ -50,7 +50,7 @@ These setup `lldb` and loads the symbols, then attaches to the process. It also
 a `clearjdb` command which you can use from within the `lldb` REPL to clear the Java
 Debugger dialog you get when you launch your app.
 
-```dotnetcli
+```shell
 lldb
 > platform select remote-android
 > platform connect connect://localhost:5039 
@@ -65,7 +65,7 @@ lldb
 
 if your symbols are in a separate `.dbg` file, you can use the following.
 
-```dotnetcli
+```
 > target symbols add samples/NativeAOT/bin/Debug/net10.0-android/android-arm64/native/NativeAOT.so.dbg
 ```
 
@@ -75,13 +75,15 @@ launching the activity.
 you can do this via the `lldb` terminal by using the `clearjdb` function which is an
 extension function we have.
 
-or use the following from the command line.
+or use the following from the command line:
 
-`python3 samples/NativeAOT/lldb_commands.py`
+```shell
+python3 samples/NativeAOT/lldb_commands.py
+```
 
 you can also clear it manually via
 
-```dotnetcli
+```shell
 adb forward --remove tcp:8700
 adb forward tcp:8700 jdwp:<pid>
 jdb -attach localhost:8700 
@@ -93,7 +95,7 @@ You will want to type `quit` to exit the `jdb` terminal once it has connected.
 
 Setting breakpoints just need to use the filename and line number, these are just standard `lldb` commands.
 
-```dotnetcli
+```
 breakpoint set -f MainActivity.cs -l 34
 ```