spotless

VERSIONING.md

@@ -5,20 +5,20 @@ the OpenTelemetry Android project.
 
 ## Versioning scheme
 
-This codebase uses [Semantic Versioning](https://semver.org/) (semver) for its version numbers. 
+This codebase uses [Semantic Versioning](https://semver.org/) (semver) for its version numbers.
 All modules in this codebase are released at the same time and, as such, will
 be versioned together. All modules in this repo are released with the same version number.
 
 Until 1.0.0 stability has been achieved, regular releases will only typically increment
 the minor version (second number in the semver triplet). Patch releases are considered
-exceptional, and will only be created if a critical issue needs to be addressed shortly after 
+exceptional, and will only be created if a critical issue needs to be addressed shortly after
 a regular release.
 
 ## Snapshot builds
 
-Every commit to the `main` branch will cause a 
+Every commit to the `main` branch will cause a
 [snapshot build](https://oss.sonatype.org/content/repositories/snapshots/io/opentelemetry/android/)
-to be published to Sonatype. Users may choose to build and test and file issues against SNAPSHOT 
+to be published to Sonatype. Users may choose to build and test and file issues against SNAPSHOT
 builds, but their use in production is strongly discouraged.
 
 ## Android API Compatibility
@@ -28,10 +28,10 @@ Android API Level 21 and above. API levels 21 to 25 require desugaring of the co
 
 The API compatibility level outlined here is aligned with the Android compatibility
 in [opentelemetry-java](https://github.com/open-telemetry/opentelemetry-java/blob/main/VERSIONING.md#language-version-compatibility).
-The minimum compatibility version is subject to change when the minimum requirement 
+The minimum compatibility version is subject to change when the minimum requirement
 for [Google Play Services](https://developers.google.com/android/guides/setup) changes.
 
-The various `auto-instrumentation` modules provided here are NOT required to follow this 
+The various `auto-instrumentation` modules provided here are NOT required to follow this
 same compatibility level. That is, certain auto-instrumentation modules MAY choose to use a
 newer minimum Android SDK level. When an instrumentation differs from the default,
 the minimum supported sdk will be listed in the `build.gradle.kts` file for that module. For example
@@ -46,7 +46,7 @@ This Android library is built on top of other OpenTelemetry components:
 * [opentelemetry-java-contrib](https://github.com/open-telemetry/opentelemetry-java-contrib)
 
 As such, this project will follow a release schedule that is related to the upstream release
-schedule. Presently, this means a monthly release, typically within a week of the last 
+schedule. Presently, this means a monthly release, typically within a week of the last
 release of the above components.
 
 ## Internal packages