Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove duplicated terms in documentation

Browse Source 
... using the following RegEx to find them:

(?<!\S)(\w+)(?:\s+\1)+(?!\S)
This commit is contained in:
Sam Brannen
2023-09-12 19:00:28 +02:00
parent 345910591a
commit b6fdfe8ee3
4 changed files with 8 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
framework-docs/modules/ROOT/pages/core/beans/classpath-scanning.adoc
View File

@@ -668,7 +668,7 @@ generated by the `BeanNameGenerator` strategy known to that scanner.
By default, the `AnnotationBeanNameGenerator` is used. For Spring
xref:core/beans/classpath-scanning.adoc#beans-stereotype-annotations[stereotype annotations],
if you supply a name via the the annotation's `value` attribute that name will be used as
if you supply a name via the annotation's `value` attribute that name will be used as
the name in the corresponding bean definition. This convention also applies when the
following JSR-250 and JSR-330 annotations are used instead of Spring stereotype
annotations: `@jakarta.annotation.ManagedBean`, `@javax.annotation.ManagedBean`,

2
framework-docs/modules/ROOT/pages/core/validation/beans-beans.adoc
View File

@@ -9,7 +9,7 @@ input:
- xref:beans-constructor-binding[Constructor binding] - bind user input to a public data
constructor, looking up constructor argument values in the user input.
- xref:beans-beans[Property binding] - bind user input to setters, matching keys from the
the user input to properties of the target object structure.
user input to properties of the target object structure.
You can apply both constructor and property binding or only one.

2
framework-docs/modules/ROOT/pages/data-access/jdbc/core.adoc
View File

@@ -824,7 +824,7 @@ between ``SQLException``s and Spring's own `org.springframework.dao.DataAccessEx
which is agnostic in regard to data access strategy. Implementations can be generic (for
example, using SQLState codes for JDBC) or proprietary (for example, using Oracle error
codes) for greater precision. This exception translation mechanism is used behind the
the common `JdbcTemplate` and `JdbcTransactionManager` entry points which do not
common `JdbcTemplate` and `JdbcTransactionManager` entry points which do not
propagate `SQLException` but rather `DataAccessException`.
NOTE: As of 6.0, the default exception translator is `SQLExceptionSubclassTranslator`,