Replace "check out" with more formal language

Update documentation to use more formal language rather than
"check out".

See gh-28503
pull/28583/head
Jay Bryant 3 years ago committed by Phillip Webb
parent b60c8b4a12
commit 9f2c8f65ee

@ -3,4 +3,4 @@
If you are interested in how the build tool plugins work, you can look at the {spring-boot-code}/spring-boot-project/spring-boot-tools[`spring-boot-tools`] module on GitHub. If you are interested in how the build tool plugins work, you can look at the {spring-boot-code}/spring-boot-project/spring-boot-tools[`spring-boot-tools`] module on GitHub.
More technical details of the executable jar format are covered in <<executable-jar#executable-jar,the appendix>>. More technical details of the executable jar format are covered in <<executable-jar#executable-jar,the appendix>>.
If you have specific build-related questions, you can check out the "`<<howto#howto, how-to>>`" guides. If you have specific build-related questions, see the "`<<howto#howto, how-to>>`" guides.

@ -1,6 +1,6 @@
[[deployment.whats-next]] [[deployment.whats-next]]
== What to Read Next == What to Read Next
Check out the https://www.cloudfoundry.org/[Cloud Foundry], https://www.heroku.com/[Heroku], https://www.openshift.com[OpenShift], and https://boxfuse.com[Boxfuse] web sites for more information about the kinds of features that a PaaS can offer. See the https://www.cloudfoundry.org/[Cloud Foundry], https://www.heroku.com/[Heroku], https://www.openshift.com[OpenShift], and https://boxfuse.com[Boxfuse] web sites for more information about the kinds of features that a PaaS can offer.
These are just four of the most popular Java PaaS providers. These are just four of the most popular Java PaaS providers.
Since Spring Boot is so amenable to cloud-based deployment, you can freely consider other providers as well. Since Spring Boot is so amenable to cloud-based deployment, you can freely consider other providers as well.

@ -1,6 +1,6 @@
[[documentation.io]] [[documentation.io]]
== IO == IO
If your application needs IO capabilities, check out this section: If your application needs IO capabilities, see one or more of the following sections:
* *Caching:* <<io#io.caching, Caching support EhCache, Hazelcast, Infinispan and more>> * *Caching:* <<io#io.caching, Caching support EhCache, Hazelcast, Infinispan and more>>
* *Quartz:* <<io#io.quartz, Quartz Scheduling>> * *Quartz:* <<io#io.quartz, Quartz Scheduling>>

@ -1,6 +1,6 @@
[[documentation.messaging]] [[documentation.messaging]]
== Messaging == Messaging
If your application uses any messaging protocol, check out this section: If your application uses any messaging protocol, see one or more of the following sections:
* *JMS:* <<messaging#messaging.jms, Auto-configuration for ActiveMQ and Artemis, Sending and Receiving messages through JMS>> * *JMS:* <<messaging#messaging.jms, Auto-configuration for ActiveMQ and Artemis, Sending and Receiving messages through JMS>>
* *AMQP:* <<messaging#messaging.amqp, Auto-configuration for RabbitMQ>> * *AMQP:* <<messaging#messaging.amqp, Auto-configuration for RabbitMQ>>

@ -1,6 +1,6 @@
[[features.whats-next]] [[features.whats-next]]
== What to Read Next == What to Read Next
If you want to learn more about any of the classes discussed in this section, you can check out the {spring-boot-api}/[Spring Boot API documentation] or you can browse the {spring-boot-code}[source code directly]. If you want to learn more about any of the classes discussed in this section, see the {spring-boot-api}/[Spring Boot API documentation] or you can browse the {spring-boot-code}[source code directly].
If you have specific questions, take a look at the <<howto#howto, how-to>> section. If you have specific questions, see the <<howto#howto, how-to>> section.
If you are comfortable with Spring Boot's core features, you can continue on and read about <<actuator#actuator, production-ready features>>. If you are comfortable with Spring Boot's core features, you can continue on and read about <<actuator#actuator, production-ready features>>.

@ -1,7 +1,7 @@
[[getting-started.whats-next]] [[getting-started.whats-next]]
== What to Read Next == What to Read Next
Hopefully, this section provided some of the Spring Boot basics and got you on your way to writing your own applications. Hopefully, this section provided some of the Spring Boot basics and got you on your way to writing your own applications.
If you are a task-oriented type of developer, you might want to jump over to https://spring.io and check out some of the https://spring.io/guides/[getting started] guides that solve specific "`How do I do that with Spring?`" problems. If you are a task-oriented type of developer, you might want to jump over to https://spring.io and follow some of the https://spring.io/guides/[getting started] guides that solve specific "`How do I do that with Spring?`" problems.
We also have Spring Boot-specific "`<<howto#howto, How-to>>`" reference documentation. We also have Spring Boot-specific "`<<howto#howto, How-to>>`" reference documentation.
Otherwise, the next logical step is to read _<<using#using>>_. Otherwise, the next logical step is to read _<<using#using>>_.

@ -7,7 +7,7 @@ include::attributes.adoc[]
This section provides answers to some common '`how do I do that...`' questions that often arise when using Spring Boot. This section provides answers to some common '`how do I do that...`' questions that often arise when using Spring Boot.
Its coverage is not exhaustive, but it does cover quite a lot. Its coverage is not exhaustive, but it does cover quite a lot.
If you have a specific problem that we do not cover here, you might want to check out https://stackoverflow.com/tags/spring-boot[stackoverflow.com] to see if someone has already provided an answer. If you have a specific problem that we do not cover here, you might want to check https://stackoverflow.com/tags/spring-boot[stackoverflow.com] to see if someone has already provided an answer.
This is also a great place to ask new questions (please use the `spring-boot` tag). This is also a great place to ask new questions (please use the `spring-boot` tag).
We are also more than happy to extend this section. We are also more than happy to extend this section.

@ -18,7 +18,7 @@ By default, the auto-configuration will try to configure the following (in order
. JSON codecs with Jackson . JSON codecs with Jackson
The `spring-boot-starter-rsocket` starter provides both dependencies. The `spring-boot-starter-rsocket` starter provides both dependencies.
Check out the <<features#features.json.jackson,Jackson support section>> to know more about customization possibilities. See the <<features#features.json.jackson,Jackson support section>> to know more about customization possibilities.
Developers can customize the `RSocketStrategies` component by creating beans that implement the `RSocketStrategiesCustomizer` interface. Developers can customize the `RSocketStrategies` component by creating beans that implement the `RSocketStrategiesCustomizer` interface.
Note that their `@Order` is important, as it determines the order of codecs. Note that their `@Order` is important, as it determines the order of codecs.

@ -280,7 +280,7 @@ Spring Boot now provides a configuration property to choose and opt in the new s
matching-strategy: "path-pattern-parser" matching-strategy: "path-pattern-parser"
---- ----
For more details on why you should consider this new implementation, please check out the For more details on why you should consider this new implementation, see the
https://spring.io/blog/2020/06/30/url-matching-with-pathpattern-in-spring-mvc[dedicated blog post]. https://spring.io/blog/2020/06/30/url-matching-with-pathpattern-in-spring-mvc[dedicated blog post].
NOTE: `PathPatternParser` is an optimized implementation but restricts usage of NOTE: `PathPatternParser` is an optimized implementation but restricts usage of
@ -666,5 +666,3 @@ JSPs are not supported when using an executable jar.
* Creating a custom `error.jsp` page does not override the default view for <<web#web.servlet.spring-mvc.error-handling,error handling>>. * Creating a custom `error.jsp` page does not override the default view for <<web#web.servlet.spring-mvc.error-handling,error handling>>.
<<web#web.servlet.spring-mvc.error-handling.error-pages,Custom error pages>> should be used instead. <<web#web.servlet.spring-mvc.error-handling.error-pages,Custom error pages>> should be used instead.

Loading…
Cancel
Save