docs: various updates for Libbulletjme v23.0.1

Author: stephengold

docs/en/modules/ROOT/pages/add.adoc

@@ -47,7 +47,7 @@ dependencies {
     implementation(
             group: "com.github.stephengold",
             name: "Libbulletjme-Android",
-            version: "23.0.0",
+            version: "23.0.1",
             classifier: "SpDebug",
             ext: "aar"
     )
@@ -63,7 +63,7 @@ it's necessary to replace `implementation` with `compile`.
 plus a set of (separately-packaged) native libraries.
 
 Because of how releases are built,
-the desktop JVM library is released under 6 distinct names (artifact IDs).
+the desktop JVM library is released under 7 distinct names (artifact IDs).
 In contrast, each desktop native library is specific to a particular platform,
 build type, and flavor.
 
@@ -79,10 +79,10 @@ repositories {
 }
 dependencies {
     // JVM library:
-    implementation("com.github.stephengold:Libbulletjme-Windows64:23.0.0")
+    implementation("com.github.stephengold:Libbulletjme-Windows64:23.0.1")
 
     // native libraries:
-    runtimeOnly("com.github.stephengold:Libbulletjme-Linux64:23.0.0:SpDebug")
+    runtimeOnly("com.github.stephengold:Libbulletjme-Linux64:23.0.1:SpDebug")
         // Native libraries for other platforms could be added.
 }
 ----
@@ -143,6 +143,7 @@ NativeDynamicLibrary[] libraries = {
     new NativeDynamicLibrary("native/linux/x86_64", PlatformPredicate.LINUX_X86_64),
     new NativeDynamicLibrary("native/osx/arm64", PlatformPredicate.MACOS_ARM_64),
     new NativeDynamicLibrary("native/osx/x86_64", PlatformPredicate.MACOS_X86_64),
+    new NativeDynamicLibrary("native/windows/arm64", PlatformPredicate.WIN_ARM_64),
     new NativeDynamicLibrary("native/windows/x86_64", PlatformPredicate.WIN_X86_64)
 };
 loader.registerNativeLibraries(libraries).initPlatformLibrary();

docs/en/modules/ROOT/pages/build.adoc

@@ -18,7 +18,7 @@ Here's the recommended procedure:
 
 . Install build software:
 .. a https://adoptium.net/releases.html[Java Development Kit (JDK)],
-  version 8 or higher, and
+  version 17 or higher, and
 .. one of the supported C++ compilers:
 ... for Linux:  https://gcc.gnu.org/[the GNU Compiler Collection] or https://www.llvm.org[Clang]
 ... for macOS:  https://developer.apple.com/xcode[Xcode]
@@ -37,7 +37,7 @@ Here's the recommended procedure:
 .. using https://git-scm.com[Git]:
 ... `git clone https://github.com/stephengold/Libbulletjme.git`
 ... `cd Libbulletjme`
-... `git checkout -b latest 23.0.0`
+... `git checkout -b latest 23.0.1`
 .. using a web browser:
 ... browse to https://github.com/stephengold/Libbulletjme/releases/latest
 ... follow the "Source code (zip)" link
@@ -51,9 +51,12 @@ Here's the recommended procedure:
 . To build Android artifacts, you'll need to
   install https://developer.android.com/studio[Android Studio]
   and point the `ANDROID_HOME` environment variable to that installation.
+. Install the Android build script:
+.. using Bash or Fish or PowerShell or Zsh: `cp android.gradle build.gradle`
+.. using Windows Command Prompt: `copy android.gradle build.gradle`
 . Run the Gradle wrapper on the Android build script:
-.. using Bash or Fish or PowerShell or Zsh: `./gradlew -b android.gradle build`
-.. using Windows Command Prompt: `.\gradlew -b android.gradle build`
+.. using Bash or Fish or PowerShell or Zsh: `./gradlew build`
+.. using Windows Command Prompt: `.\gradlew build`
 
 After a successful build,
 artifacts will be found in "build/libs" (desktop) and "build/outputs/aar" (Android).
@@ -87,13 +90,3 @@ You can install them to your local Maven repository.
 
 After a successful build,
 your local copy of the site will be found in "docs/build/site".
-
-
-== Cleanup
-
-At any time, you can restore the project to a pristine state:
-
-* using Bash or Fish or PowerShell or Zsh: `./gradlew clean;./gradlew -b android.gradle clean`
-* using Windows Command Prompt:
-** `.\gradlew clean`
-** `.\gradlew -b android.gradle clean`

docs/en/modules/ROOT/pages/debug.adoc

@@ -11,7 +11,7 @@ During development, Java assertions should be enabled using:
 
 Similarly, native-code assertions should be enabled during development,
 by loading a native library of the "debug" type,
-such as "com.github.stephengold:Libbulletjme-Linux64:23.0.0:SpDebug".
+such as "com.github.stephengold:Libbulletjme-Linux64:23.0.1:SpDebug".
 
 
 == Visualization

docs/en/modules/ROOT/pages/implementation.adoc

@@ -31,9 +31,9 @@ compiled for the {url-enwiki}/Computing_platform[platform]
 on which the app is executing.
 
 The {Project} project publishes native libraries
-for 10 different platforms:
+for 11 different platforms:
 
-* Windows (64-bit),
+* Windows (x86-64 and ARM64),
 * Linux (x86-64, armhf, and aarch64),
 * macOS (x86-64 and ARM64), and
 * Android (armeabi-v7a, arm64-v8a, x86, and x86_64).