From 3ae5978fc7ae345996c9d84a1260df00339a323c Mon Sep 17 00:00:00 2001
From: IDJack <798979047@qq.com>
Date: Thu, 19 Jan 2023 18:57:55 +0800
Subject: [PATCH] Fix typo in testing-native-application.adoc

---
 .../docs/asciidoc/native-image/testing-native-applications.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/testing-native-applications.adoc b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/testing-native-applications.adoc
index 434aed5bf3fe..c2f39893b731 100644
--- a/spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/testing-native-applications.adoc
+++ b/spring-boot-project/spring-boot-docs/src/docs/asciidoc/native-image/testing-native-applications.adoc
@@ -46,7 +46,7 @@ Or you might consider using a project like Selenium to check your application's
 [[native-image.testing.with-native-build-tools]]
 === Testing With Native Build Tools
 GraalVM Native Build Tools includes the ability to run tests inside a native image.
-This can be helpful when you want to deeply test that the internals of you application work in a GraalVM native image.
+This can be helpful when you want to deeply test that the internals of your application work in a GraalVM native image.
 
 Generating the native image that contains the tests to run can be a time-consuming operation, so most developers will probably prefer to use the JVM locally.
 They can, however, be very useful as part of a CI pipeline.