Fix typos (#10124)

19 files changed, 27 insertions, 27 deletions

diff --git a/documentation/articles/ComponentAddonProjectSetupHOWTO.asciidoc b/documentation/articles/ComponentAddonProjectSetupHOWTO.asciidoc
index a0730f45bd..e8d063e27c 100644
--- a/documentation/articles/ComponentAddonProjectSetupHOWTO.asciidoc
+++ b/documentation/articles/ComponentAddonProjectSetupHOWTO.asciidoc
@@ -96,7 +96,7 @@ src directory from Navigator view and select Team -> Add to Index. Then
 add the rest of the files (.settings, .project, .classpath and target)
 to .gitignore with Team -> Ignore. Finally, just do Team -> Commit.
 
-At this point - or later whenevery you are ready for it - you can
+At this point - or later whenever you are ready for it - you can
 publish the project to GitHub. Just go to github.com and create a new
 repository. Use MyList as the name for the repository. Then follow the
 instructions on the screen. In my case, I executed the following command
@@ -123,12 +123,12 @@ for Maven run configuration for "jetty:run". Now when you make any
 changes to server-side code - for example to `WidgetTestApplication.java`
 - hit save and reload the browser pointing to
 http://localhost:8080/mylist/?restartApplication, the changes are
-appliead immediately. Even better - you can start the project with Debug
+applied immediately. Even better - you can start the project with Debug
 As and add break points to the application.
 
 Client-side changes are more tricky as they are compiled from Java to
 JavaScript by GWT. To make those changes immediately you, must be
-running a GWT Devepment Mode. This is done by running Maven goal gwt:run
+running a GWT Development Mode. This is done by running Maven goal gwt:run
 instead of just pointing your web browser to the running application.
 Note that must be running both jetty:run and gwt:run concurrently.
 gwt:run starts application called "GWT Development Mode". From there you
diff --git a/documentation/articles/ConfigureInputFieldsToGuideDataEntry.asciidoc b/documentation/articles/ConfigureInputFieldsToGuideDataEntry.asciidoc
index 8c32561ab1..cb08a16951 100644
--- a/documentation/articles/ConfigureInputFieldsToGuideDataEntry.asciidoc
+++ b/documentation/articles/ConfigureInputFieldsToGuideDataEntry.asciidoc
@@ -22,7 +22,7 @@ image:img/form1.png[Basic form]
 The shape, size and layout of these fields don’t really correspond to
 the kinds of values expected to be entered in them, or to the relations
 between different fields. For instance, while the homepage url is
-probably between 25 and 55 characters long, european postal codes are
+probably between 25 and 55 characters long, European postal codes are
 only about 6 digits long, and age maxes out at three digits. By setting
 the widths of these fields to be approximately proportional to the
 lengths of expected values, the fields become easier to identify, and
diff --git a/documentation/articles/CreatingASimpleComponentContainer.asciidoc b/documentation/articles/CreatingASimpleComponentContainer.asciidoc
index 5e25aa2144..7a94c85ec8 100644
--- a/documentation/articles/CreatingASimpleComponentContainer.asciidoc
+++ b/documentation/articles/CreatingASimpleComponentContainer.asciidoc
@@ -13,7 +13,7 @@ and `ComponentContainer`{empty}s. ComponentContainers are Components in
 themselves which can also contain other components. If you are about to
 implement a component that contains other components, then you'll get a
 headstart by extending Vaadin's `ComponentContainer`. The biggest feature
-is in tranferring the list of server side components from your component
+is in transferring the list of server side components from your component
 to the client. Here's how you do it.
 
 [[server-side]]
diff --git a/documentation/articles/CreatingAThemeUsingSass.asciidoc b/documentation/articles/CreatingAThemeUsingSass.asciidoc
index 4e3ca2c77c..0b1babae76 100644
--- a/documentation/articles/CreatingAThemeUsingSass.asciidoc
+++ b/documentation/articles/CreatingAThemeUsingSass.asciidoc
@@ -135,7 +135,7 @@ that the name matches your themename, or your styles will not be
 applied._
 
 Some of the nice features you get with Sass include variables, selector
-nesting, mixins (optionally with paramaters), selector inheritance. For
+nesting, mixins (optionally with parameters), selector inheritance. For
 more information of what you can do with Sass, you should refer to the
 official documentation at http://sass-lang.com
 
diff --git a/documentation/articles/EnableAndDisableButtonsToIndicateState.asciidoc b/documentation/articles/EnableAndDisableButtonsToIndicateState.asciidoc
index c963d8533a..4acc90440b 100644
--- a/documentation/articles/EnableAndDisableButtonsToIndicateState.asciidoc
+++ b/documentation/articles/EnableAndDisableButtonsToIndicateState.asciidoc
@@ -59,7 +59,7 @@ spared the trouble of attempting in vain to perform the action, and the
 nuisance of an error message.
 
 image:img/potus2.png[Save and Revert actions disabled when they cannot be
-succesfully
+successfully
 performed.]
 
 [[disablingenabling-actions-to-indicate-state]]
diff --git a/documentation/articles/FindingTheCurrentUIAndPageAndVaadinSession.asciidoc b/documentation/articles/FindingTheCurrentUIAndPageAndVaadinSession.asciidoc
index 6be26d18d9..ad2c3b7a7b 100644
--- a/documentation/articles/FindingTheCurrentUIAndPageAndVaadinSession.asciidoc
+++ b/documentation/articles/FindingTheCurrentUIAndPageAndVaadinSession.asciidoc
@@ -47,7 +47,7 @@ public void buttonClick(ClickEvent event) {
 }
 ....
 
-And finally similiarly for `Page`. For instance adding a browser window
+And finally similarly for `Page`. For instance adding a browser window
 resize listener can be added like this:
 
 [source,java]
diff --git a/documentation/articles/IIInjectionAndScopes.asciidoc b/documentation/articles/IIInjectionAndScopes.asciidoc
index cbf843ebde..f8aa692bd8 100644
--- a/documentation/articles/IIInjectionAndScopes.asciidoc
+++ b/documentation/articles/IIInjectionAndScopes.asciidoc
@@ -147,7 +147,7 @@ public class UserInfo implements Serializable {
 ....
 
 We'll inject that to the UI and assign the user some name during
-initalization (for now)
+initialization (for now)
 
 [source,java]
 ....
diff --git a/documentation/articles/IntegrationExperiences.asciidoc b/documentation/articles/IntegrationExperiences.asciidoc
index 8680a690f0..2ae8ab3f43 100644
--- a/documentation/articles/IntegrationExperiences.asciidoc
+++ b/documentation/articles/IntegrationExperiences.asciidoc
@@ -96,7 +96,7 @@ with hierarchical table aka treetable. Another simple but important
 widget was multilingual text field. It acts just like normal textfield
 but when opened, you get the java field opened with multiple locale
 instances, it has nice UI too including user friendly flags. Great for
-handling i18n based data in your UI. We got multiple customercases that
+handling i18n based data in your UI. We got multiple customer cases that
 enjoy these new widgets. -*Jani Laakso*
 ===============================
 
@@ -259,7 +259,7 @@ business logic inside UI logic, there's no need to. This way the UI can
 be replaced in the future and also when updating old systems to use
 Vaadin (e.g. SWING applications that are written this way) it has been a
 breeze when the only thing that needs to be rewritten is the UI. Another
-very imporant factor is security, trust your data layer, do not trust
+very important factor is security, trust your data layer, do not trust
 your clients, using enterprise beans with JNDI helps you. Scalability
 and high-availability are also easier to cope with. Scale up with
 multiple cheap Tomcat machines acting as Vaadin clients, few powerful
diff --git a/documentation/articles/LoadTestingWithGatling.asciidoc b/documentation/articles/LoadTestingWithGatling.asciidoc
index c13b84098c..a76a579066 100644
--- a/documentation/articles/LoadTestingWithGatling.asciidoc
+++ b/documentation/articles/LoadTestingWithGatling.asciidoc
@@ -30,7 +30,7 @@ properly.
 The communication that Vaadin's "thin client" in browser does with the
 server side has couple of checks that it does to improve robustness and
 security. One can simulate these with Gatling as well, by e.g.
-https://github.com/mstahv/v-quiz/blob/master/src/test/scala/loadtest/WebSocketVaadinSimulation.scala#L84[reading the XSRF preventation key into a variable] and passing the value
+https://github.com/mstahv/v-quiz/blob/master/src/test/scala/loadtest/WebSocketVaadinSimulation.scala#L84[reading the XSRF prevention key into a variable] and passing the value
 https://github.com/mstahv/v-quiz/blob/master/src/test/scala/loadtest/WebSocketVaadinSimulation.scala#L95[in
 each response]. However, these setting can be disabled during load
 testing to make it easier to write and maintain your application. The
@@ -43,7 +43,7 @@ separate maven profile and inject different parameters with it.
 Disabling XSRF presentation key
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-The XSRF preventation can be disabled with following servlet parameter
+The XSRF prevention can be disabled with following servlet parameter
 (or similar servlet 3 style parameter). NOTE, do not leave this for
 public apps in production.
 
@@ -117,7 +117,7 @@ communication channel, WebSockets, you can do that with Gatling as well.
 Using the recorder in this case doesn't work, but handcrafting the test
 case isn't that hard once you get started. The example app has a branch
 with WebSocket test case. With WebSocket communication it might also be
-handy to disable xsrf preventation and the so called "syncid".
+handy to disable xsrf prevention and the so called "syncid".
 
 First two request are just normal http requests. The first gets the
 "host page" and also the initial state request is done with normal XHR.
@@ -161,7 +161,7 @@ message that the server sends when you connect to it. 
 
 Check out this script for
 https://github.com/mstahv/v-quiz/blob/master/src/test/scala/loadtest/WebSocketVaadinSimulation.scala[an
-example using WebSocket] communication. It also saves XSRF preventation
+example using WebSocket] communication. It also saves XSRF prevention
 key to variable, so it don't need it to be disabled from the server.
 
 [[configuring-gatling-to-the-web-app-build]]
diff --git a/documentation/articles/MVCBasicsInITMillToolkit.asciidoc b/documentation/articles/MVCBasicsInITMillToolkit.asciidoc
index 78b2f4848b..3f4f24d318 100644
--- a/documentation/articles/MVCBasicsInITMillToolkit.asciidoc
+++ b/documentation/articles/MVCBasicsInITMillToolkit.asciidoc
@@ -13,7 +13,7 @@ The Goal
 
 image:img/moduleDesign.jpg[1]
 
-We want to create a simple UI following the MVC pattern using the IT Mill Toolkit. The project components need to have low coupling and follow an enterprise design. In our example we also want to retrieve information from a database and display it in the view. The different parts of the UI need also to be able to communicate with eachother.
+We want to create a simple UI following the MVC pattern using the IT Mill Toolkit. The project components need to have low coupling and follow an enterprise design. In our example we also want to retrieve information from a database and display it in the view. The different parts of the UI need also to be able to communicate with each other.
 
 We have divided the project in two layers; A UI layer, which purpose is to display information to the user, and a Data layer which has no knowledge of the Toolkit and which is only responsible for retrieving and storing data. The reason for dividing the project up in these layers is so that, if we choose, we can easily use multiple servers.
 
diff --git a/documentation/articles/OptimizingSluggishUI.asciidoc b/documentation/articles/OptimizingSluggishUI.asciidoc
index a3a7ffae66..4f4d98e60c 100644
--- a/documentation/articles/OptimizingSluggishUI.asciidoc
+++ b/documentation/articles/OptimizingSluggishUI.asciidoc
@@ -94,8 +94,8 @@ http://uilder.virtuallypreinstalled.com/run/deepcomponenttrees/?restartApplicati
 layouts when possible
 * Do you need to extend CustomComponent in your server side composition
 or could you just extend some layout? This will result having one
-component less in the component tree. You might sometimes be argueing
-against this because of architectual reasons (CustomComponent has a
+component less in the component tree. You might sometimes be arguing
+against this because of architectural reasons (CustomComponent has a
 fewer methods than VerticalLayout), but on the other hand Java has
 interfaces to deal the issue in a cleaner manner.
 * Maybe you have an  extra layout inside your Panel or Window (see
diff --git a/documentation/articles/ReadOnlyVsDisabledFields.asciidoc b/documentation/articles/ReadOnlyVsDisabledFields.asciidoc
index 80f054f531..3d9ae230fb 100644
--- a/documentation/articles/ReadOnlyVsDisabledFields.asciidoc
+++ b/documentation/articles/ReadOnlyVsDisabledFields.asciidoc
@@ -96,7 +96,7 @@ one might expect. Doing the same with _disabled does_, though.)
 One caveat regarding read-only fields is that if the text is longer than
 the field, it will be clipped, as opposed to a Label, which instead will
 wrap the text to a new line. Thus, in certain situations, switching to
-Labels may be preferrable.
+Labels may be preferable.
 
 It’s probably best to mention here that *setReadOnly(true)* also has a
 certain side-effect in Vaadin that *setEnabled(false)* does not: You
diff --git a/documentation/articles/SettingAndReadingCookies.asciidoc b/documentation/articles/SettingAndReadingCookies.asciidoc
index 3a310e7d96..1027c60bbb 100644
--- a/documentation/articles/SettingAndReadingCookies.asciidoc
+++ b/documentation/articles/SettingAndReadingCookies.asciidoc
@@ -13,7 +13,7 @@ http://en.wikipedia.org/wiki/HTTP_cookie[cookies] from both the server
 and the client side in Vaadin, with one caveat: Cookies are not possible
 if you enable Push using WebSocket (see tickets
 http://dev.vaadin.com/ticket/11808[11808] and
-http://dev.vaadin.com/ticket/12518[12518]). Begining in Vaadin 7.6,
+http://dev.vaadin.com/ticket/12518[12518]). Beginning in Vaadin 7.6,
 cookies can be used with the WEBSOCKET_XHR transport type.
 
 The
diff --git a/documentation/articles/SettingAndReadingSessionAttributes.asciidoc b/documentation/articles/SettingAndReadingSessionAttributes.asciidoc
index 4d96c47e5c..72db6bef11 100644
--- a/documentation/articles/SettingAndReadingSessionAttributes.asciidoc
+++ b/documentation/articles/SettingAndReadingSessionAttributes.asciidoc
@@ -14,7 +14,7 @@ data, e.g. how long it should be kept around and what parts of the code
 should have access to it.
 
 1.  Store the data as a field in your UI subclass. The data is easily
-accesible from components belonging to that UI instance and the data
+accessible from components belonging to that UI instance and the data
 will be gone when the UI is closed.
 2.  Store data in the `VaadinServiceSession`. The data is easily
 accessible from any UI belonging to the same VaadinServlet or
diff --git a/documentation/articles/UsingFontIcons.asciidoc b/documentation/articles/UsingFontIcons.asciidoc
index 3741163156..7713f48c74 100644
--- a/documentation/articles/UsingFontIcons.asciidoc
+++ b/documentation/articles/UsingFontIcons.asciidoc
@@ -54,7 +54,7 @@ Making a custom set of icons
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 There are many tools for making icons, and icon fonts. One of our
-favourite tools is http://icomoon.io/app[IcoMoon], which is an excellent
+favorite tools is http://icomoon.io/app[IcoMoon], which is an excellent
 online application where you can pick icons from a vast library of
 ready-made icon fonts, to compose your own set of icons. When you’re
 done, you can download a zip that contains your font files - just copy
@@ -67,7 +67,7 @@ automatically)
 4.  Mark the icons you want in your font
 5.  _Download_ the font
 
-In IcoMoon you can also produce a customised version of FontAwesome, if
+In IcoMoon you can also produce a customized version of FontAwesome, if
 you for instance want to remove unused icons, or swap individual icons.
 You can also re-upload your custom icon font, if you want to make
 changes or additions to it later. 
diff --git a/documentation/articles/UsingVaadinInIBMDomino.asciidoc b/documentation/articles/UsingVaadinInIBMDomino.asciidoc
index 25a28bd7ad..35ffcbc8d4 100644
--- a/documentation/articles/UsingVaadinInIBMDomino.asciidoc
+++ b/documentation/articles/UsingVaadinInIBMDomino.asciidoc
@@ -286,7 +286,7 @@ image:img/domino15.png[15]
 com.paulwithers.helloVaadinFeature.
 image:img/domino16.png[16]
 
-27. Click Next and initialise from the com.paulwithers.helloVaadin
+27. Click Next and initialize from the com.paulwithers.helloVaadin
 plugin.
 
 28. Select *File* > *New* > *Update Site Project*. Call it
diff --git a/documentation/articles/Vaadin7SpringSecurityBaseAuthentification.asciidoc b/documentation/articles/Vaadin7SpringSecurityBaseAuthentification.asciidoc
index 4881d35c2d..4350274539 100644
--- a/documentation/articles/Vaadin7SpringSecurityBaseAuthentification.asciidoc
+++ b/documentation/articles/Vaadin7SpringSecurityBaseAuthentification.asciidoc
@@ -11,7 +11,7 @@ Vaadin 7 + Spring Security (base authentication)
 Vaadin 7 is easy to integrate with Spring Security. You should configure only
 2 files. First - web.xml and second one spring-security.xml (user
 credentials and security settings). This is a small example on how to use
-base form for authentification.
+base form for authentication.
 
 [[web.xml-configuration]]
 web.xml Configuration
diff --git a/documentation/articles/VaadinCDI.asciidoc b/documentation/articles/VaadinCDI.asciidoc
index 99b1efd16d..16d4cbc323 100644
--- a/documentation/articles/VaadinCDI.asciidoc
+++ b/documentation/articles/VaadinCDI.asciidoc
@@ -55,7 +55,7 @@ necessary and might in some cases even cause conflicts. +
 * *Objects must be injected* and managed by the CDI implementation in
 order to use CDI features.
 ** *Use @Inject on an instance field* to make the CDI implementation
-inject a managed intstance of the corresponding type.
+inject a managed instance of the corresponding type.
 ** *Annotate your UI class with @CDIUI("")* to let Vaadin CDI know that
 it should inject and use instances of that class when the application is
 opened in the browser.
diff --git a/documentation/articles/VaadinOnGrailsDatabaseAccess.asciidoc b/documentation/articles/VaadinOnGrailsDatabaseAccess.asciidoc
index fdf6ffab0e..0b3f847773 100644
--- a/documentation/articles/VaadinOnGrailsDatabaseAccess.asciidoc
+++ b/documentation/articles/VaadinOnGrailsDatabaseAccess.asciidoc
@@ -145,7 +145,7 @@ Database connection
 +++++++++++++++++++
 
 As we have covered big part of normal work when developing an
-application, created the persistance layer, maybe next questions are
+application, created the persistence layer, maybe next questions are
 coming. Where are the data stored? What database is used and how to
 change it?