Replace 'via' with 'over' or 'through' in the documentation

Closes gh-33878
This commit is contained in:
Moritz Halbritter
2023-01-18 16:56:42 +01:00
parent b5cebed120
commit e8d809fe65
99 changed files with 146 additions and 135 deletions

View File

@@ -818,7 +818,7 @@ Alternatively, additional auto-configurations can be added for any use of a slic
In this example, the `com.example.IntegrationAutoConfiguration` is enabled on every test annotated with `@JdbcTest`.
TIP: You can use comments via `#` in this file.
TIP: You can use comments with `#` in this file.
TIP: A slice or `@AutoConfigure...` annotation can be customized this way as long as it is meta-annotated with `@ImportAutoConfiguration`.

View File

@@ -42,7 +42,7 @@ The above configuration allows Neo4j-related beans in the application to communi
[[howto.testing.slice-tests]]
=== Structure `@Configuration` classes for inclusion in slice tests
Slice tests work by restricting Spring Framework's component scanning to a limited set of components based on their type.
For any beans that are not created via component scanning, for example, beans that are created using the `@Bean` annotation, slice tests will not be able to include/exclude them from the application context.
For any beans that are not created through component scanning, for example, beans that are created using the `@Bean` annotation, slice tests will not be able to include/exclude them from the application context.
Consider this example:
[source,java,indent=0,subs="verbatim"]

View File

@@ -1,6 +1,6 @@
[[io.whats-next]]
== What to Read Next
You should now have a good understanding of Spring Boot's <<features#features, core features>> and the various technologies that Spring Boot provides support for via auto-configuration.
You should now have a good understanding of Spring Boot's <<features#features, core features>> and the various technologies that Spring Boot provides support for through auto-configuration.
The next few sections go into detail about deploying applications to cloud platforms.
You can read about <<container-images#container-images, building container images>> in the next section or skip to the <<actuator#actuator, production-ready features>> section.