From d30e013a730e29dd7263fe9cd87f8f0acdc06fa0 Mon Sep 17 00:00:00 2001 From: Moritz Halbritter Date: Fri, 13 Jun 2025 14:17:33 +0200 Subject: [PATCH] Fix typo in "Troubleshoot Native Image Run-Time Errors" --- .../native-image/guides/troubleshoot-run-time-errors.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference-manual/native-image/guides/troubleshoot-run-time-errors.md b/docs/reference-manual/native-image/guides/troubleshoot-run-time-errors.md index bebc655c10cd..bd45ded6aed2 100644 --- a/docs/reference-manual/native-image/guides/troubleshoot-run-time-errors.md +++ b/docs/reference-manual/native-image/guides/troubleshoot-run-time-errors.md @@ -21,7 +21,7 @@ In some cases, you need to provide the analysis with configuration to make all d Failing to do so will result in an image that terminates at run-time with hard-to-diagnose errors once the dynamic feature is used in the application. This can be avoided by eagerly checking for missing metadata. -1. Pass the `--exact-reachablity-metadata` option to the `native-image` tool and rebuild the application. If you want to do this only for a specific package, specify a package prefix `--exact-reachablity-metadata=[package prefix]`. +1. Pass the `--exact-reachability-metadata` option to the `native-image` tool and rebuild the application. If you want to do this only for a specific package, specify a package prefix `--exact-reachability-metadata=[package prefix]`. > This option was introduced in GraalVM for JDK 23 and will become the default in the next feature release. It is equivalent to the `-H:ThrowMissingRegistrationErrors=` host option. @@ -68,4 +68,4 @@ Pass the `--diagnostics-mode` option enabling diagnostics output for class initi ### Related Documentation -* [Specifying Metadata with JSON](../ReachabilityMetadata.md#specifying-metadata-with-json) \ No newline at end of file +* [Specifying Metadata with JSON](../ReachabilityMetadata.md#specifying-metadata-with-json)