vale: fix ThereIs occurences

jouni · jouni · commit 202e48ff5f3f · 2022-10-12T11:45:53.000+03:00
diff --git a/articles/advanced/application-lifecycle.asciidoc b/articles/advanced/application-lifecycle.asciidoc
@@ -199,7 +199,6 @@ public class MainLayout extends Div {
 }
 ----
 
-There is more to be done.
 When a session is closed from one UI, any other UIs attached to it are left hanging.
 When the client-side engine notices that a UI and the session are gone on the server side, it displays a `Session Expired` message and, by default, reloads the UI when the message is clicked.
 
diff --git a/articles/advanced/loading-indicator.asciidoc b/articles/advanced/loading-indicator.asciidoc
@@ -50,7 +50,7 @@ public class AppShell implements AppShellConfigurator, VaadinServiceInitListener
 
 The configuration object can be used to configure the delays after which the indicator changes "stages".
 The indicator is shown after a delay of 300ms by default and given a class name of `first`.
-There are two additional delays which you can configure.
+You can configure two additional delays.
 After the delays, the class names `second` and `third` are set, which can be used to change the style of the loading indicator after a certain time has passed.
 
 [source,java]
diff --git a/articles/advanced/long-running-tasks.adoc b/articles/advanced/long-running-tasks.adoc
@@ -73,7 +73,7 @@ This happens because Vaadin is waiting for the long-running task to finish befor
 The recommended way to handle long-running tasks is to use an asynchronous approach.
 This means that the long-running task is executed in a separate thread, and the UI isn't blocked while the task is running.
 
-There are several ways to achieve an asynchronous model.
+An asynchronous model can be achieved in several ways.
 But in the context of a Spring Boot application, one way is to use the [annotationname]`@Async` annotation.
 The [annotationname]`@Async` annotation is used to mark a method as an asynchronous task.
 From the Vaadin UI side, a response to the user request is immediately sent back to the browser, and thus the user can continue interacting with the application right away without being blocked by the long-running task.
diff --git a/articles/advanced/modifying-the-bootstrap-page.asciidoc b/articles/advanced/modifying-the-bootstrap-page.asciidoc
@@ -18,7 +18,7 @@ The _Application Shell_ in Vaadin is also known as the _Bootstrap Page_, or [fil
 == Modifying the Application Shell
 
 In Vaadin 15 and later, the developer has full control of the contents of [filename]`index.html`.
-There are various ways to modify it:
+You can modify it in various ways:
 
 . On the client side, by editing [filename]`frontend/index.html` when the content is static, for instance the `<viewport>` tag.
 . On the server side, for changes that require some dynamic server content, or when Java syntax is preferred; for example, making the application installable by enabling the `@PWA` built-in feature.
diff --git a/articles/binding-data/components-binder-validation.asciidoc b/articles/binding-data/components-binder-validation.asciidoc
@@ -249,7 +249,7 @@ binder.forField(yearOfBirthField)
 
 === Implementing the Converter Interface
 
-There are two methods to implement in the [interfacename]`Converter` interface:
+You need to implement two methods from the [interfacename]`Converter` interface:
 
 * [methodname]`convertToModel()` receives a value that originates from the user.
 ** The method returns a [classname]`Result` that contains either a converted value or a conversion error message.
diff --git a/articles/components/charts/timeline.asciidoc b/articles/components/charts/timeline.asciidoc
@@ -13,8 +13,7 @@ as well as navigating between such ranges. It's especially useful when working w
 Adding a timeline to your chart is very easy - set the 'timeline' property to 'true',
 that is, call [methodname]`setTimeline(true)`.
 You can enable the timeline in a chart that displays one or more time series.
-Most of the chart types support the timeline.
-There are few exceptions which are listed here:
+Most of the chart types support the timeline, with these exceptions:
 <<charttypes#charts.charttypes.pie, `pie`>>,
 <<charttypes#charts.charttypes.gauge, `gauge`>>,
 <<charttypes#charts.charttypes.solidgauge, `solidgauge`>>,
diff --git a/articles/components/grid/flow.asciidoc b/articles/components/grid/flow.asciidoc
@@ -491,7 +491,7 @@ Conceptually, there are three types of renderer:
 
 === Using Basic Renderers
 
-There are several basic renderers that you can use to configure grid columns.
+You can use several basic renderers to configure grid columns.
 
 ==== Local Date Renderer
 
diff --git a/articles/components/upload/flow.asciidoc b/articles/components/upload/flow.asciidoc
@@ -12,7 +12,7 @@ A [classname]`Receiver` instance should be specified to receive uploaded data.
 The receiver provides an [interfacename]`OutputStream` for the framework, where it writes the content of the received file.
 You can implement the interface directly, or use the prebuilt helpers that buffer the file content for later access.
 
-There are a number of built-in implementations of [classname]`Receiver`:
+The built-in implementations of [classname]`Receiver` are:
 
  * [classname]`FileBuffer`
  * [classname]`MemoryBuffer`
diff --git a/articles/configuration/node-js.asciidoc b/articles/configuration/node-js.asciidoc
@@ -29,7 +29,7 @@ To force node installation into the home directory in development mode, you shou
 == Proxy Settings for Downloading the Front-End Toolchain
 
 If you are behind a proxy server, you should configure your proxy settings so that Vaadin can use them to download the front-end toolchain.
-There are four places that Vaadin reads proxy settings from.
+Vaadin reads proxy settings from four places.
 You can set your proxy data in any of the following:
 
 . system properties
diff --git a/articles/contributing-docs/style-guide/formatting-style.asciidoc b/articles/contributing-docs/style-guide/formatting-style.asciidoc
@@ -118,7 +118,7 @@ HK$99.99
 
 pass:[<!-- vale Vaadin.Abbr = YES -->]
 
-There is no strict rule for forming country codes in this context.
+No strict rule exists for forming country codes in this context.
 Make sure that it's clear which country is being referred to.
 
 == Dates
diff --git a/articles/contributing-docs/style-guide/style.asciidoc b/articles/contributing-docs/style-guide/style.asciidoc
@@ -97,7 +97,7 @@ Avoid using exclamation marks in technical documentation, unless it's as part of
 Its use in normal text is distracting and detracts from the professional tone.
 For example:
 
-pass:[<!-- vale Google.Exclamation = NO -->]
+pass:[<!-- vale Vaadin.Exclamation = NO -->]
 
 [example]
 ====
@@ -106,6 +106,8 @@ You have now created your component! +++[+++Avoid this usage.+++]+++
 `#!/bin/bash` +++[+++The exclamation mark is part of the script syntax.+++]+++
 ====
 
+pass:[<!-- vale Vaadin.Exclamation = YES -->]
+
 == Future Tense
 Avoid using the future tense to describe the expected behavior of something.
 Instead, use the present tense.
@@ -406,11 +408,15 @@ A _proper noun_ is a word or phrase that's the name of something or somebody; fo
 
 It's distinct from a _common noun_, which is the "standard" type of noun that identifies the nature of something or somebody; for example, a _building_, a _republic_, an _ocean_, a _band_, an _operating system_.
 
+pass:[<!-- vale Vaadin.ThereIs = NO -->]
+
 _Proper nouns_ are usually denoted by being capitalized.
 There are a small number of exceptions to this, usually by the choice of the person or organization that "owns" the name; for example, _macOS_.
 In these cases, we should try to use the "official" styling.
 If you aren't sure of the correct form, an internet search is usually enough to find it.
 
+pass:[<!-- vale Vaadin.ThereIs = YES -->]
+
 == Scanning
 _Scanning_ is the process by which a reader quickly overviews the text to evaluate the content.
 The reader does this in order to find out whether it really does contain the information that they are looking for.
diff --git a/articles/create-ui/creating-components/basic.asciidoc b/articles/create-ui/creating-components/basic.asciidoc
@@ -30,7 +30,7 @@ public class TextField extends Component {
 [TIP]
 You can use predefined constants in the `@Tag` annotation.
 For example, the `@Tag("input")` annotation is equivalent to `@Tag(Tag.INPUT)`.
-There are constants for most, but not all, tag names.
+Most tag names have a constant, but not all.
 
 == Adding an API
 
diff --git a/articles/create-ui/creating-components/events.asciidoc b/articles/create-ui/creating-components/events.asciidoc
@@ -180,7 +180,7 @@ For example, text input events are fired while the user types.
 
 You can configure the rate at which events are sent to the server by defining different `debounce` settings in the `@DomEvent` annotation.
 Debouncing always requires a `timeout` (in milliseconds) and a burst `phase`, which determines when events are sent to the server.
-There are three burst phase options:
+You have three burst phase options:
 
 * `LEADING` phase: An event is sent at the beginning of a burst, but subsequent events are only sent after one timeout period has passed without any new events.
 This is useful for things like button clicks, to prevent accidental double submissions.
diff --git a/articles/create-ui/creating-components/extending-component.asciidoc b/articles/create-ui/creating-components/extending-component.asciidoc
@@ -144,7 +144,7 @@ See <<{articles}/styling/custom-theme/styling-components#,Styling Components>> f
 Vaadin client-side components are based on http://polymer-library.polymer-project.org/3.0/docs/about_30[Polymer 3], which supports extending existing components.
 You can use the `extends` property to extend existing Polymer elements.
 
-There are five ways to inherit a template from another Polymer element:
+A template can be inherited from another Polymer element in five ways:
 
 . Inheriting a base class template without modifying it.
 . Overriding a base class template in a child class.
diff --git a/articles/create-ui/enabled-state.asciidoc b/articles/create-ui/enabled-state.asciidoc
@@ -206,11 +206,10 @@ public String getProp() {
 
 === Enabling DOM Events
 
-There are two ways to enable DOM events.
-You can use:
+You can enable DOM events in two ways:
 
-. an [methodname]`addEventListener()` overload method in the `Element` API, or
-. the `@DomEvent` annotation.
+. with an [methodname]`addEventListener()` overload method in the `Element` API, or
+. with the `@DomEvent` annotation.
 
 *Example*: Unblocking a DOM event for a disabled element using the [methodname]`addEventListener()` overload method that accepts the `DisabledUpdateMode.ALWAYS` parameter.
 
diff --git a/articles/create-ui/shortcut.asciidoc b/articles/create-ui/shortcut.asciidoc
@@ -261,9 +261,12 @@ input.addFocusShortcut(Key.KEY_F)
         // if a text field is focused
         .allowBrowserDefault();
 ----
+pass:[<!-- vale Vaadin.ThereIs = NO -->]
 
 There is one exception to these rules: by default, click shortcuts created with the [methodname]`ClickNotifier::addClickShortcut(Key, KeyModifier...)` method allow default browser behavior.
 
+pass:[<!-- vale Vaadin.ThereIs = YES -->]
+
 == Checking Shortcut States
 
 [classname]`ShortcutRegistration` offers a variety of methods to check the internal state of a shortcut, and all configurable values that have corresponding getter methods.
diff --git a/articles/create-ui/templates/polymer/event-handlers.asciidoc b/articles/create-ui/templates/polymer/event-handlers.asciidoc
@@ -285,18 +285,14 @@ See <<bindings#,PolymerTemplate, Binding Model Data>> for how to get the model v
 
 === Additional Ways to Call the Server
 
-There are two additional ways to call the server:
-
-pass:[<!-- vale Vale.Spelling = NO -->]
+You can call the server in two additional ways:
 
 * Use the `@ClientCallable` annotation.
 This annotation allows a Java method to be called from client-side code, using the `this.$server._serverMethodName(args)_` notation.
 You can use this anywhere in your client-side Polymer class implementation.
 You can pass your own arguments to the method, as long as the types match the server-side method declaration.
 See <<{articles}/create-ui/element-api/client-server-rpc#clientcallable-annotation,@ClientCallable Annotation>> for more.
 
-pass:[<!-- vale Vale.Spelling = YES -->]
-
 * You can also define [classname]`PropertyChangeListeners` when working with templates.
 See  <<{articles}/create-ui/enabled-state#enabling-property-changes,Enabling Property Changes>> for more.
 
diff --git a/articles/create-ui/templates/polymer/model-bean.asciidoc b/articles/create-ui/templates/polymer/model-bean.asciidoc
@@ -163,7 +163,7 @@ No method that can return the original bean exists.
 Its only purpose is to update the values of the model.
 
 [WARNING]
-There is currently no way to get a detached bean from the model.
+It's impossible to get a detached bean from the model.
 
 == Using Model Data with an Entity Manager
 
diff --git a/articles/guide/start/gradle.asciidoc b/articles/guide/start/gradle.asciidoc
@@ -570,7 +570,7 @@ When the list of dependencies causes the classpath to go over a set limit on Win
 In some cases, when running a Spring Boot application, the resource loader doesn't load the classpath packages correctly from the manifest.
 The failed annotation scanning makes the required `npm` packages unavailable.
 
-There are two ways to fix this:
+You can fix this in two ways:
 
 - add the repository `mavenLocal()` to <<#build-file.repositories,build file repositories>>
 - specify the `vaadin.whitelisted-packages` property; see <<../../integrations/spring/configuration#,Vaadin Spring Configuration>>
diff --git a/articles/guide/start/maven-archetype.asciidoc b/articles/guide/start/maven-archetype.asciidoc
@@ -31,6 +31,8 @@ mvn -B archetype:generate \
 
 The parameters are as follows:
 
+pass:[<!-- vale Vaadin.ThereIs = NO -->]
+
 `archetypeGroupId`::
 The group ID of the archetype is `com.vaadin` for Vaadin archetypes.
 
@@ -58,6 +60,8 @@ For example, if the group ID is `com.example` and the artifact ID is `myproject`
 The initial version number of your application.
 The number must follow the Maven version numbering format.
 
+pass:[<!-- vale Vaadin.ThereIs = YES -->]
+
 Creating a project can take a while, as Maven fetches all the dependencies.
 
 
diff --git a/articles/integrations/cdi/index.asciidoc b/articles/integrations/cdi/index.asciidoc
@@ -65,7 +65,7 @@ In practice, because other Java EE/Jakarta EE features are used together with CD
 
 == Configuring the Vaadin CDI Add-On
 
-There are no specific CDI configuration options.
+No specific CDI configuration options exist.
 
 An instance of the CDI-enabled Vaadin servlet, `com.vaadin.cdi.CdiVaadinServlet`, is deployed automatically, provided you don't setup a Vaadin servlet in your [filename]`web.xml` or use the `@WebServlet` annotation.
 You can also customize `CdiVaadinServlet` to suit your setup.
diff --git a/articles/integrations/embedding/exporter.asciidoc b/articles/integrations/embedding/exporter.asciidoc
@@ -251,7 +251,7 @@ public class LoginForm extends Div {
 * The example uses several Vaadin components: `FormLayout`, `TextField`, `PasswordField` and `Button`.
 * The code takes care of authentication and sets an authentication token in the [classname]`HttpSession`, which makes it available while the session is live.
 * Because the main application servlet uses the same [classname]`HttpSession` instance, it changes behavior and redirects authenticated users to the main servlet, which now shows content specific to authenticated users.
-There are various ways to do this:
+You can do this in various ways:
 ** Execute JavaScript directly from your Java code and set the location to `"/example"` : `getUI().get().getPage().executeJs("window.location.href='/example'");`.
 ** Use a solution similar to this example; design the component code so that its logic is isolated and it doesn't need to know anything about the embedding context.
 This method allows you to decouple the embedded component logic completely from the application that uses it.
diff --git a/articles/integrations/embedding/push.asciidoc b/articles/integrations/embedding/push.asciidoc
@@ -9,7 +9,7 @@ layout: page
 
 You can configure and enable Push in your embedded applications.
 
-There are two ways to configure Push:
+You can configure Push in two ways:
 
 * Use the <<../../advanced/server-push#push.configuration.annotation,`@Push` annotation>> in your [classname]`WebComponentExporter` class.
 +
diff --git a/articles/integrations/osgi/advanced.asciidoc b/articles/integrations/osgi/advanced.asciidoc
@@ -278,7 +278,7 @@ public class MainView extends Div {
 
 Doing this would avoid having to get a service programmatically and creating a fallback handler, as described earlier.
 
-There are several reasons why this isn't supported:
+This isn't supported because of several reasons:
 
 * It cannot work with OSGi Declarative Services.
 The [classname]`MainView` would need to be a service by itself, which requires quite error-prone boilerplate code, such as defining it with: `@Component(scope=ServiceScope.PROTOTYPE, service=SomeDedicatedService.class)`
diff --git a/articles/integrations/osgi/index.asciidoc b/articles/integrations/osgi/index.asciidoc
@@ -195,7 +195,7 @@ Vaadin-OSGi-Extender: true
 
 To have your application running under OSGi container, you need to have Vaadin Flow bundles deployed.
 The application bundle can then be deployed and started.
-There are many transitive dependencies that also need to be deployed.
+Many transitive dependencies also need to be deployed.
 The bundle isn't activated unless all its dependencies are deployed and activated.
 Some OSGi containers might deploy transitive dependencies along with the bundle deployment.
 
diff --git a/articles/integrations/osgi/karaf.asciidoc b/articles/integrations/osgi/karaf.asciidoc
@@ -13,7 +13,7 @@ layout: page
 The Karaf `http` feature along with the `war` feature provides an implementation of HTTP Whiteboard, which is the standard in Karaf in practice.
 This implementation is known as Pax Web (see HTTP feature details http://karaf.apache.org/manual/latest-2.x/users-guide/http.html[here]).
 Pax Web isn't fully compliant with the HTTP Whiteboard OSGi Compendium 7 specification.
-There are some issues related to [classname]`ServletContextListener` support.
+[classname]`ServletContextListener` support has some issues.
 Because of these issues, the recommended way of registering `VaadinServlet`, described in the generic <<index#,Using Vaadin with OSGi>> tutorial, doesn't work in Pax Web.
 
 Nevertheless, it's still possible to use Vaadin OSGi support with Pax Web.
diff --git a/articles/integrations/portlet/handling-portlet-phases.asciidoc b/articles/integrations/portlet/handling-portlet-phases.asciidoc
@@ -163,8 +163,7 @@ public class MyView extends Div implements PortletView {
 
 === Using Handler Interfaces
 
-There is another way to listen to changes in window state and portlet mode.
-In this way, instead of [interfacename]`PortletView`, your view should implement the [interfacename]`WindowStateHandler` and/or the [interfacename]`PortletModeHandler` interface.
+Another way to listen to changes in window state and portlet mode, instead of [interfacename]`PortletView`, is to implement the [interfacename]`WindowStateHandler` and/or the [interfacename]`PortletModeHandler` interface in your view.
 The following example shows how to react to changes to window state using [interfacename]`WindowStateHandler` interface, and changes to portlet mode using the [interfacename]`PortletModeHandler` interface.
 
 [source,java]
diff --git a/articles/integrations/spring/routing.asciidoc b/articles/integrations/spring/routing.asciidoc
@@ -68,7 +68,7 @@ public class DataBeanImpl implements DataBean {
 
 == Routing in Spring Boot and WAR Applications
 
-There is a difference between running an application as a Spring Boot application and as a `WAR` application deployed to a web server.
+Running an application as a Spring Boot application is different from running it as a `WAR` application deployed to a web server.
 
 In `WAR` applications, all `@Route` annotations are discovered automatically, due to the Servlet 3.0 specification.
 With Spring Boot applications, this is, by design, not the case.
diff --git a/articles/routing/additional-guides/route-templates.asciidoc b/articles/routing/additional-guides/route-templates.asciidoc
@@ -44,7 +44,7 @@ Route template parameters are defined as segments within [annotationname]`@Route
 
 Parameter values may be retrieved from a [classname]`BeforeEvent` instance on any [classname]`Component` in the navigation chain, either parent layout or navigation target.
 Parameter values are strings.
-There are convenience methods for converting them to numeric and Boolean types.
+You can use convenience methods for converting them to numeric and Boolean types.
 These are described later.
 
 Values may be empty, except if the parameter is defined in the last segment.
diff --git a/articles/routing/dynamic.asciidoc b/articles/routing/dynamic.asciidoc
@@ -219,7 +219,7 @@ if (getCurrentUser().hasAccessToReporting()) {
 == Example: Adding a New View on User Log-in
 
 This example demonstrates how to add a new view on user log-in.
-There are two types of users: admin users and normal users.
+Two types of users exist: admin users and normal users.
 After log-in, we show a different view, depending on the user's access rights.
 
 The demo application contains:
@@ -281,7 +281,7 @@ public class InfoView extends Div {
 ----
 
 After log-in, we want to add a new route, depending on the access rights of the user.
-There are two available targets:
+We have two available targets:
 
 * [classname]`AdminView` class.
 +
diff --git a/articles/routing/page-titles.asciidoc b/articles/routing/page-titles.asciidoc
@@ -6,7 +6,7 @@ layout: page
 
 = Updating the Page Title During Navigation
 
-There are two ways to update the page title during navigation:
+You can update the page title in two ways during navigation:
 
 . Use the `@PageTitle` annotation.
 . Implement [interfacename]`HasDynamicTitle`.
diff --git a/articles/security/enabling-security.adoc b/articles/security/enabling-security.adoc
@@ -163,7 +163,7 @@ public class SecurityService {
 == Security Configuration Class
 
 The next step is to have a Spring Security class that extends [classname]`VaadinWebSecurity`.
-There is no convention for naming this class, so in this documentation it's named [classname]`SecurityConfiguration`.
+There's no convention for naming this class, so in this documentation it's named [classname]`SecurityConfiguration`.
 However, take care with Spring Security annotations.
 Here is a minimal implementation of such a class:
 
diff --git a/articles/styling/getting-started.adoc b/articles/styling/getting-started.adoc
@@ -339,7 +339,7 @@ We have to use here the `:host()` shadow function because the `toggle-button` pa
 [[styling.get-started.sub-component-styling]]
 == How to Selectively Style a Sub-component of a Vaadin Component
 
-There are cases in which we cannot use CSS class names to do the selective styling.
+In some cases we cannot use CSS class names to do the selective styling.
 Specifically, we cannot rely on CSS class names when we want to style the sub-components of a Vaadin component.
 
 What do we mean by a sub-component? Some Vaadin components create sub-components that exist in the DOM independently from the Vaadin component itself.
diff --git a/articles/styling/lumo/design-tokens/styling-using-design-tokens.adoc b/articles/styling/lumo/design-tokens/styling-using-design-tokens.adoc
diff --git a/articles/styling/theme-annotation.adoc b/articles/styling/theme-annotation.adoc
diff --git a/articles/testing/end-to-end/maven.adoc b/articles/testing/end-to-end/maven.adoc
diff --git a/articles/testing/end-to-end/page-objects.adoc b/articles/testing/end-to-end/page-objects.adoc
diff --git a/articles/testing/end-to-end/reliable-tests.adoc b/articles/testing/end-to-end/reliable-tests.adoc
diff --git a/articles/testing/end-to-end/test-grid.adoc b/articles/testing/end-to-end/test-grid.adoc
diff --git a/articles/testing/ui-unit/component-query.adoc b/articles/testing/ui-unit/component-query.adoc
diff --git a/articles/tools/designer/getting-started/wrap-up.asciidoc b/articles/tools/designer/getting-started/wrap-up.asciidoc
diff --git a/articles/tools/mpr/introduction/3-legacy-uis.asciidoc b/articles/tools/mpr/introduction/3-legacy-uis.asciidoc
diff --git a/articles/tools/mpr/introduction/3-spring-boot.asciidoc b/articles/tools/mpr/introduction/3-spring-boot.asciidoc
diff --git a/articles/tutorial/components-and-layouts.adoc b/articles/tutorial/components-and-layouts.adoc
diff --git a/articles/tutorial/forms-and-validation.adoc b/articles/tutorial/forms-and-validation.adoc
diff --git a/articles/tutorial/production-deployment.adoc b/articles/tutorial/production-deployment.adoc
diff --git a/articles/upgrading/upgrade-tool/fusion/_22-23.adoc b/articles/upgrading/upgrade-tool/fusion/_22-23.adoc

Original file line number	Diff line number	Diff line change
`@@ -199,7 +199,6 @@ public class MainLayout extends Div {`
`199`	`199`	`}`
`200`	`200`	`----`
`201`	`201`
`202`		`-There is more to be done.`
`203`	`202`	`When a session is closed from one UI, any other UIs attached to it are left hanging.`
`204`	`203`	When the client-side engine notices that a UI and the session are gone on the server side, it displays a `Session Expired` message and, by default, reloads the UI when the message is clicked.
`205`	`204`