Polish

See gh-19409

spring-boot-project/spring-boot-docs/src/main/asciidoc/deployment.adoc

@@ -54,7 +54,7 @@ For example, using a `Dockerfile` you could express it in this form:
 	ENTRYPOINT ["java","-cp","app:app/lib/*","com.example.MyApplication"]
 ----
 
-Assuming the above `Dockerfile` is the current directory, your docker image can be built with `docker build .`, or optionally specifying the path to your application jar, as shown in the following example:
+Assuming the above `Dockerfile` is in the current directory, your docker image can be built with `docker build .`, or optionally specifying the path to your application jar, as shown in the following example:
 
 [indent=0]
 ----

spring-boot-project/spring-boot-docs/src/main/asciidoc/howto.adoc

@@ -1636,7 +1636,7 @@ Spring Data can create implementations of `@Repository` interfaces of various fl
 Spring Boot handles all of that for you, as long as those `@Repositories` are included in the same package (or a sub-package) of your `@EnableAutoConfiguration` class.
 
 For many applications, all you need is to put the right Spring Data dependencies on your classpath.
-There is a `spring-boot-starter-data-jpa` for JPA, spring-boot-starter-data-mongodb` for Mongodb, etc.
+There is a `spring-boot-starter-data-jpa` for JPA, `spring-boot-starter-data-mongodb` for Mongodb, etc.
 To get started, create some repository interfaces to handle your `@Entity` objects.
 
 Spring Boot tries to guess the location of your `@Repository` definitions, based on the `@EnableAutoConfiguration` it finds.

spring-boot-project/spring-boot-docs/src/main/asciidoc/spring-boot-features.adoc

@@ -5074,7 +5074,7 @@ For example, you might declare the following section in `application.properties`
 	spring.rabbitmq.password=secret
 ----
 
-Alternatively, you could configure the same connection using the `addresses` attributes:
+Alternatively, you could configure the same connection using the `addresses` attribute:
 
 [source,properties,indent=0]
 ----