Enforce one-sentence-per-line rule in adoc (spring-attic#1345)

Bring existing ascii docs into compliance with one-sentence-per-line adoc best practice
https://asciidoctor.org/docs/asciidoc-recommended-practices/#one-sentence-per-line

Author: elefeint

CODE_OF_CONDUCT.adoc

@@ -2,12 +2,7 @@
 
 == Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 == Our Standards
 
@@ -33,40 +28,25 @@ Examples of unacceptable behavior by participants include:
 
 == Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 == Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+Representation of a project may be further defined and clarified by project maintainers.
 
 == Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team.
+All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
+The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
 Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 
 == Attribution
 
-This Code of Conduct is adapted from the https://www.contributor-covenant.org[Contributor
-Covenant], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+This Code of Conduct is adapted from the https://www.contributor-covenant.org[Contributor Covenant], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

CONTRIBUTING.adoc

@@ -1,32 +1,24 @@
 = Code formatting guidelines
 
-The directory src/eclipse has two files for use with code formatting, `eclipse-code-formatter.xml`
-for the majority of the code formatting rules and `eclipse.importorder` to order the import
-statements.
+The directory src/eclipse has two files for use with code formatting, `eclipse-code-formatter.xml` for the majority of the code formatting rules and `eclipse.importorder` to order the import statements.
 
 == Eclipse
 Import these files by navigating `Windows -> Preferences` and then the menu items
 `Preferences > Java > Code Style > Formatter` and `Preferences > Java > Code Style >
 Organize Imports` respectively.
 
 == IntelliJ IDEA
-Install the plugin `Eclipse Code Formatter`. You can find it by searching in "Browse Repositories",
-under `Settings > Plugins` within IDEA (Once installed, you will need to reboot IDEA for it to take
-effect).
+Install the plugin `Eclipse Code Formatter`.
+You can find it by searching in "Browse Repositories", under `Settings > Plugins` within IDEA (Once installed, you will need to reboot IDEA for it to take effect).
 
-Then navigate to `Settings > Other Settings` (this might be under `Preferences` on Mac) and select
-the Eclipse Code Formatter.
-Select the `eclipse-code-formatter.xml` file for the field `Eclipse Java Formatter config file` and
-the file `eclipse.importorder` for the field `Import order`.
-Enable the `Eclipse code formatter` by clicking `Use the Eclipse code formatter` radio button at the
-top of the page, then click the *OK* button.
+Then navigate to `Settings > Other Settings` (this might be under `Preferences` on Mac) and select the Eclipse Code Formatter.
+Select the `eclipse-code-formatter.xml` file for the field `Eclipse Java Formatter config file` and the file `eclipse.importorder` for the field `Import order`.
+Enable the `Eclipse code formatter` by clicking `Use the Eclipse code formatter` radio button at the top of the page, then click the *OK* button.
 
-* NOTE: If you configure the `Eclipse Code Formatter` from `File > Other Settings > Default
-Settings`, it will set this policy across all of your IDEA projects.
+* NOTE: If you configure the `Eclipse Code Formatter` from `File > Other Settings > Default Settings`, it will set this policy across all of your IDEA projects.
 
-* IDEA's "Optimize imports on the fly" option turned on interferes with the Eclipse code formatter
-import optimization. Consider disabling the option if optimization does not yield the expected
-results.
+* IDEA's "Optimize imports on the fly" option turned on interferes with the Eclipse code formatter import optimization.
+Consider disabling the option if optimization does not yield the expected results.
 
 = Contributing a patch
 
@@ -45,4 +37,5 @@ Guide]
 
 6. Ensure your code has an appropriate set of unit tests which all pass
 
-7. Submit a pull request. It will be approved and merged by a committer
+7. Submit a pull request.
+It will be approved and merged by a committer

README.adoc

@@ -85,7 +85,7 @@ Our starters handle the object instantiation and configuration logic so you don'
 Every starter depends on the GCP starter to provide critical bits of configuration, like the GCP project ID or OAuth2 credentials location.
 You can configure these as properties in, for example, a properties file:
 
-[source, yaml]
+[source]
 ----
 spring.cloud.gcp.project-id=[YOUR_GCP_PROJECT_ID]
 spring.cloud.gcp.credentials.location=file:[LOCAL_PRIVATE_KEY_FILE]

docs/src/main/asciidoc/config.adoc

@@ -53,7 +53,7 @@ NOTE: Core properties, as described in <<spring-cloud-gcp-core,Spring Cloud GCP
 In other words, if `spring.application.name` is `myapp` and `spring.profiles.active` is `prod`, the configuration should be called `myapp_prod`.
 +
 In order to do that, you should have the https://cloud.google.com/sdk/[Google Cloud SDK] installed, own a Google Cloud Project and run the following command:
-+
+[source]
 ----
 gcloud init # if this is your first Google Cloud SDK run.
 gcloud beta runtime-config configs create myapp_prod
@@ -62,12 +62,14 @@ gcloud beta runtime-config configs variables set myapp.queue-size 25 --config-na
 
 2. Configure your `bootstrap.properties` file with your application's configuration data:
 +
+[source]
 ----
 spring.application.name=myapp
 spring.profiles.active=prod
 ----
 3. Add the `@ConfigurationProperties` annotation to a Spring-managed bean:
 +
+[source]
 ----
 @Component
 @ConfigurationProperties("myapp")

docs/src/main/asciidoc/core.adoc

@@ -68,7 +68,7 @@ It uses the `spring.cloud.gcp.credentials.location` property to locate the OAuth
 Keep in mind this property is a Spring Resource, so the credentials file can be obtained from a number of https://docs.spring.io/spring/docs/current/spring-framework-reference/html/resources.html#resources-implementations[different locations] such as the file system, classpath, URL, etc.
 The next example specifies the credentials location property in the file system.
 
-[source,yaml]
+[source]
 ----
 spring.cloud.gcp.credentials.location=file:/usr/local/key.json
 ----
@@ -109,14 +109,14 @@ To do that, specify a comma-delimited list of https://developers.google.com/iden
 
 `spring.cloud.gcp.credentials.scopes` is a comma-delimited list of https://developers.google.com/identity/protocols/googlescopes[Google OAuth2 scopes] for Google Cloud Platform services that the credentials returned by the provided `CredentialsProvider` support.
 
-[source,yaml]
+[source]
 ----
 spring.cloud.gcp.credentials.scopes=https://www.googleapis.com/auth/pubsub,https://www.googleapis.com/auth/sqlservice.admin
 ----
 
 You can also use `DEFAULT_SCOPES` placeholder as a scope to represent the starters default scopes, and append the additional scopes you need to add.
 
-[source,yaml]
+[source]
 ----
 spring.cloud.gcp.credentials.scopes=DEFAULT_SCOPES,https://www.googleapis.com/auth/cloud-vision
 ----

docs/src/main/asciidoc/datastore.adoc

@@ -64,8 +64,7 @@ The following configuration options are available:
 |===
 | Name | Description | Required | Default value
 | `spring.cloud.gcp.datastore.enabled` | Enables the Cloud Datastore client | No | `true`
-| `spring.cloud.gcp.datastore.project-id` | GCP project ID where the Google Cloud Datastore API
-is hosted, if different from the one in the <<spring-cloud-gcp-core,Spring Cloud GCP Core Module>>
+| `spring.cloud.gcp.datastore.project-id` | GCP project ID where the Google Cloud Datastore API is hosted, if different from the one in the <<spring-cloud-gcp-core,Spring Cloud GCP Core Module>>
 | No |
 | `spring.cloud.gcp.datastore.credentials.location` | OAuth2 credentials for authenticating with the
 Google Cloud Datastore API, if different from the ones in the
@@ -116,7 +115,8 @@ public class Trader {
 }
 ----
 
-Spring Data Cloud Datastore will ignore any property annotated with `@Transient`. These properties will not be written to or read from Cloud Datastore.
+Spring Data Cloud Datastore will ignore any property annotated with `@Transient`.
+These properties will not be written to or read from Cloud Datastore.
 
 ==== Constructors
 
@@ -220,13 +220,11 @@ In addition, all types that can be converted to the ones listed in the table by
 
 Custom converters can be used extending the type support for user defined types.
 
-. Converters need to implement the `org.springframework.core.convert.converter.Converter` interface in
-both directions.
+. Converters need to implement the `org.springframework.core.convert.converter.Converter` interface in both directions.
 
 . The user defined type needs to be mapped to one of the basic types supported by Cloud Datastore.
 
-. An instance of both Converters (read and write) needs to be passed to the `DatastoreCustomConversions` constructor,
-which then has to be made available as a `@Bean` for `DatastoreCustomConversions`.
+. An instance of both Converters (read and write) needs to be passed to the `DatastoreCustomConversions` constructor, which then has to be made available as a `@Bean` for `DatastoreCustomConversions`.
 
 For example:
 
@@ -306,17 +304,15 @@ Elements are converted to Cloud Datastore supported types individually. `byte[]`
 
 ==== Custom Converter for collections
 Users can provide converters from  `List<?>` to the custom collection type.
-Only read converter is necessary, the Collection API is used on the write side to convert a collection to
-the internal list type.
+Only read converter is necessary, the Collection API is used on the write side to convert a collection to the internal list type.
 
 Collection converters need to implement the `org.springframework.core.convert.converter.Converter` interface.
 
 
 Example:
 
 Let's improve the Singer class from the previous example.
-Instead of a field of type `Album`,
-we would like to have a field of type `ImmutableSet<Album>`:
+Instead of a field of type `Album`, we would like to have a field of type `ImmutableSet<Album>`:
 
 [source, java]
 ----
@@ -703,7 +699,8 @@ In the example above the first two reads utilize keys, while the third is execut
 
 ===== Indexes
 
-By default, all fields are indexed. To disable indexing on a particular field, `@Unindexed` annotation can be used.
+By default, all fields are indexed.
+To disable indexing on a particular field, `@Unindexed` annotation can be used.
 
 Example:
 [source, java]
@@ -763,15 +760,17 @@ DatastoreOperations myDatastoreOperations;
 public String doWorkInsideTransaction() {
   return myDatastoreOperations.performTransaction(
     transactionDatastoreOperations -> {
-      // work with transactionDatastoreOperations here. It is also a DatastoreOperations object.
+      // Work with transactionDatastoreOperations here.
+      // It is also a DatastoreOperations object.
 
       return "transaction completed";
     }
   );
 }
 ----
 
-The `performTransaction` method accepts a `Function` that is provided an instance of a `DatastoreOperations` object. The final returned value and type of the function is determined by the user.
+The `performTransaction` method accepts a `Function` that is provided an instance of a `DatastoreOperations` object.
+The final returned value and type of the function is determined by the user.
 You can use this object just as you would a regular `DatastoreOperations` with an exception:
 
 - It cannot perform sub-transactions.
@@ -861,7 +860,7 @@ Filtering parameters can be of types supported by your configured custom convert
 [source, java]
 ----
 public interface TradeRepository extends DatastoreRepository<Trade, String[]> {
-    List<Trader> findByAction(String action);
+  List<Trader> findByAction(String action);
 
   int countByAction(String action);
 
@@ -892,7 +891,8 @@ Cloud Datastore only supports filter components joined by AND, and the following
 After writing a custom repository interface specifying just the signatures of these methods, implementations are generated for you and can be used with an auto-wired instance of the repository.
 Because of Cloud Datastore's requirement that explicitly selected fields must all appear in a composite index together, `find` name-based query methods are run as `SELECT *`.
 
-Delete queries are also supported. For example, query methods such as `deleteByAction` or `removeByAction` delete entities found by `findByAction`.
+Delete queries are also supported.
+For example, query methods such as `deleteByAction` or `removeByAction` delete entities found by `findByAction`.
 Delete queries are executed as separate read and delete operations instead of as a single transaction because Cloud Datastore cannot query in transactions unless ancestors for queries are specified.
 As a result, `removeBy` and `deleteBy` name-convention query methods cannot be used inside transactions via either `performInTransaction` or `@Transactional` annotation.
 
@@ -902,13 +902,11 @@ Delete queries can have the following return types:
 * A collection of entities that were deleted
 * 'void'
 
-Methods can have `org.springframework.data.domain.Pageable` parameter to control pagination and sorting,
-or `org.springframework.data.domain.Sort` parameter to control sorting only.
+Methods can have `org.springframework.data.domain.Pageable` parameter to control pagination and sorting, or `org.springframework.data.domain.Sort` parameter to control sorting only.
 See https://docs.spring.io/spring-data/data-commons/docs/current/reference/html/#repositories.query-methods[Spring Data documentation] for details.
 
 For returning multiple items in a repository method, we support Java collections as well as `org.springframework.data.domain.Page` and `org.springframework.data.domain.Slice`.
-If a method's return type is `org.springframework.data.domain.Page`, the returned object will include current page,
-total number of results and total number of pages.
+If a method's return type is `org.springframework.data.domain.Page`, the returned object will include current page, total number of results and total number of pages.
 
 NOTE: Methods that return `Page` execute an additional query to compute total number of pages.
 Methods that return `Slice`, on the other hand, don't execute any additional queries and therefore are much more efficient.
@@ -948,14 +946,16 @@ The following parameter types are supported:
 * `java.lang.Double`
 * `java.lang.Long`
 * `java.lang.String`
-* `enum` values. These are queried as `String` values.
+* `enum` values.
+These are queried as `String` values.
 
 With the exception of `Cursor`, array forms of each of the types are also supported.
 
 If you would like to obtain the count of items of a query or if there are any items returned by the query, set the `count = true` or `exists = true` properties of the `@Query` annotation, respectively.
 The return type of the query method in these cases should be an integer type or a boolean type.
 
-Cloud Datastore provides provides the `SELECT __key__ FROM ...` special column for all kinds that retrieves the `Key`s of each row. Selecting this special `__key__` column is especially useful and efficient for `count` and `exists` queries.
+Cloud Datastore provides provides the `SELECT __key__ FROM ...` special column for all kinds that retrieves the `Key`s of each row.
+Selecting this special `__key__` column is especially useful and efficient for `count` and `exists` queries.
 
 You can also query for non-entity types:
 
@@ -1034,7 +1034,8 @@ DatastoreRepository myRepo;
 public String doWorkInsideTransaction() {
   return myRepo.performTransaction(
     transactionDatastoreRepo -> {
-      // work with the single-transaction transactionDatastoreRepo here. This is a DatastoreRepository object.
+      // Work with the single-transaction transactionDatastoreRepo here.
+      // This is a DatastoreRepository object.
 
       return "transaction completed";
     }
@@ -1044,7 +1045,8 @@ public String doWorkInsideTransaction() {
 
 ==== Projections
 
-Spring Data Cloud Datastore supports {spring-data-commons-ref}/#projections[projections]. You can define projection interfaces based on domain types and add query methods that return them in your repository:
+Spring Data Cloud Datastore supports {spring-data-commons-ref}/#projections[projections].
+You can define projection interfaces based on domain types and add query methods that return them in your repository:
 
 [source, java]
 ----