spellchecking

src/en/guide/GORM/advancedGORMFeatures/ormdsl/caching.gdoc

@@ -103,5 +103,5 @@ Below is a description of the different cache settings and their usages:
 
 * @read-only@ - If your application needs to read but never modify instances of a persistent class, a read-only cache may be used.
 * @read-write@ - If the application needs to update data, a read-write cache might be appropriate.
-* @nonstrict-read-write@ - If the application only occasionally needs to update data (ie. if it is very unlikely that two transactions would try to update the same item simultaneously) and strict transaction isolation is not required, a @nonstrict-read-write@ cache might be appropriate.
+* @nonstrict-read-write@ - If the application only occasionally needs to update data (i.e. if it is very unlikely that two transactions would try to update the same item simultaneously) and strict transaction isolation is not required, a @nonstrict-read-write@ cache might be appropriate.
 * @transactional@ - The @transactional@ cache strategy provides support for fully transactional cache providers such as JBoss TreeCache. Such a cache may only be used in a JTA environment and you must specify @hibernate.transaction.manager_lookup_class@ in the @grails-app/conf/DataSource.groovy@ file's @hibernate@ config.

src/en/guide/GORM/advancedGORMFeatures/ormdsl/tableAndColumnNames.gdoc

@@ -33,7 +33,7 @@ Here @firstName@ is a dynamic method within the @mapping@ Closure that has a sin
 
 h4. Column type
 
-GORM supports configuration of Hibernate types with the DSL using the type attribute. This includes specifing user types that implement the Hibernate [org.hibernate.usertype.UserType|api:org.hibernate.usertype.UserType] interface, which allows complete customization of how a type is persisted. As an example if you had a @PostCodeType@ you could use it as follows:
+GORM supports configuration of Hibernate types with the DSL using the type attribute. This includes specifying user types that implement the Hibernate [org.hibernate.usertype.UserType|api:org.hibernate.usertype.UserType] interface, which allows complete customization of how a type is persisted. As an example if you had a @PostCodeType@ you could use it as follows:
 
 {code:java}
 class Address {

src/en/guide/GORM/domainClasses/sets,ListsAndMaps.gdoc

@@ -8,7 +8,7 @@ class Author {
 }
 {code}
 
-The books property that GORM injects is a @java.util.Set@. Sets guarantee uniquenes but not order, which may not be what you want. To have custom ordering you configure the Set as a @SortedSet@:
+The books property that GORM injects is a @java.util.Set@. Sets guarantee uniqueness but not order, which may not be what you want. To have custom ordering you configure the Set as a @SortedSet@:
 
 {code}
 class Author {

src/en/guide/GORM/querying/criteria.gdoc

@@ -256,7 +256,7 @@ def accountNumber = results.getLong('number')
 To quote the documentation of Hibernate ScrollableResults:
 
 {quote}
-A result iterator that allows moving around within the results by arbitrary increments. The Query / ScrollableResults pattern is very similar to the JDBC PreparedStatement/ ResultSet pattern and the semantics of methods of this interface are similar to the similarly named methods on ResultSet.
+A result iterator that allows moving around within the results by arbitrary increments. The Query / ScrollableResults pattern is very similar to the JDBC PreparedStatement / ResultSet pattern and the semantics of methods of this interface are similar to the similarly named methods on ResultSet.
 {quote}
 
 Contrary to JDBC, columns of results are numbered from zero.

src/en/guide/GORM/querying/detachedCriteria.gdoc

@@ -104,7 +104,7 @@ def results = Person.withCriteria {
  }
 {code}
 
-Notice that in this case the subquery class is the same as the original criteria query class (ie. @Person@) and hence the query can be shortened to:
+Notice that in this case the subquery class is the same as the original criteria query class (i.e. @Person@) and hence the query can be shortened to:
 
 {code}
 def results = Person.withCriteria {

src/en/guide/async/asyncRequests.gdoc

@@ -6,7 +6,7 @@ The reason being that with an asynchronous / non-blocking response, the one thre
 
 For example, if you have 70 available container threads and an action takes a minute to complete, if the actions are not executed in a non-blocking fashion the likelihood of all 70 threads being occupied and the container not being able to respond is quite high and you should consider asynchronous request processing.
 
-Since Grails 2.3, Grails features a simplified API for creating asynchronous responses built on the @Promise@ mechism discussed previously.
+Since Grails 2.3, Grails features a simplified API for creating asynchronous responses built on the @Promise@ mechanism discussed previously.
 
 The implementation is based on Servlet 3.0 async so to enable the async features you need to set your servlet target version to 3.0 in BuildConfig.groovy: 
 

src/en/guide/async/promises.gdoc

@@ -150,7 +150,7 @@ import grails.async.*
 Promises.promiseFactory = new SynchronousPromiseFactory()
 {code}
 
-Using the @PromiseFactory@ mechanism is theoritically possible to plug in other concurrency libraries into the Grails framework.
+Using the @PromiseFactory@ mechanism is theoretically possible to plug in other concurrency libraries into the Grails framework.
 
 h3. DelegateAsync Transformation
 

src/en/guide/commandLine/forkedMode.gdoc

@@ -40,9 +40,9 @@ grails.project.fork = [
 ]
 {code}
 
-h4. Using the Test Runnner Deamon to Speed-up Test Execution
+h4. Using the Test Runner Daemon to Speed-up Test Execution
 
-The defaut configuration for the testing is to activate a daemon to run tests using the @daemon@ argument:
+The default configuration for the testing is to activate a daemon to run tests using the @daemon@ argument:
 
 {code}
 grails.project.fork = [

src/en/guide/commandLine/interactiveMode.gdoc

@@ -20,4 +20,4 @@ Note that with \! (bang) commands, you get file path auto completion - ideal for
 
 The @stop-app@ command will stop an application that has been run with the @run-app@ command.
 
-To exit interactive mode enter the @exit@ command.  Note that if the Grails application has been run with @run-app@ normally it will terminate when the interactive mode console exits because the JVM will be terminated. An exception to this would be if the application were running in forked mode which means the application is running in a different JVM.  In that case the application will be left running afer the interactive mode console terminates.  If you want to exit interactive mode and stop an application that is running in forked mode, use the @quit@ command.  The @quit@ command will stop the running application and then close interactive mode.
+To exit interactive mode enter the @exit@ command.  Note that if the Grails application has been run with @run-app@ normally it will terminate when the interactive mode console exits because the JVM will be terminated. An exception to this would be if the application were running in forked mode which means the application is running in a different JVM.  In that case the application will be left running after the interactive mode console terminates.  If you want to exit interactive mode and stop an application that is running in forked mode, use the @quit@ command.  The @quit@ command will stop the running application and then close interactive mode.

src/en/guide/conf/config/builtInOptions.gdoc

@@ -34,7 +34,7 @@ On the runtime front, i.e. @Config.groovy@, there are quite a few more core sett
 h3. War generation
 
 * @grails.project.war.file@ - Sets the name and location of the WAR file generated by the [war|commandLine] command
-* @grails.war.dependencies@ - A closure containing Ant builder syntax or a list of JAR filenames. Lets you customise what libaries are included in the WAR file.
+* @grails.war.dependencies@ - A closure containing Ant builder syntax or a list of JAR filenames. Lets you customise what libraries are included in the WAR file.
 * @grails.war.copyToWebApp@ - A closure containing Ant builder syntax that is legal inside an Ant copy, for example "fileset()". Lets you control what gets included in the WAR file from the "web-app" directory.
 * @grails.war.resources@ - A closure containing Ant builder syntax. Allows the application to do any other work before building the final WAR file
 

src/en/guide/conf/config/logging.gdoc

@@ -92,7 +92,7 @@ This example configures loggers with names starting with 'org.codehaus.groovy.gr
 
 In other words, loggers are hierarchical. This makes configuring them by package much simpler than it would otherwise be.
 
-The most common things that you will want to capture log output from are your controllers, services, and other artifacts. Use the convention mentioned earlier to do that: _grails.app.<artifactType>.<className>_. In particular the class name must be fully qualifed, i.e. with the package if there is one:
+The most common things that you will want to capture log output from are your controllers, services, and other artifacts. Use the convention mentioned earlier to do that: _grails.app.<artifactType>.<className>_. In particular the class name must be fully qualified, i.e. with the package if there is one:
 
 {code:java}
 log4j = {

src/en/guide/conf/dataSource.gdoc

@@ -153,7 +153,7 @@ h4. More on dbCreate
 
 Hibernate can automatically create the database tables required for your domain model. You have some control over when and how it does this through the @dbCreate@ property, which can take these values:
 
-* *create* - Drops the existing schemaCreates the schema on startup, dropping existing tables, indexes, etc. first.
+* *create* - Drops the existing schema and creates the schema on startup, dropping existing tables, indexes, etc. first.
 * *create-drop* - Same as *create*, but also drops the tables when the application shuts down cleanly.
 * *update* - Creates missing tables and indexes, and updates the current schema without dropping any tables or data. Note that this can't properly handle many schema changes like column renames (you're left with the old column containing the existing data).
 * *validate* - Makes no changes to your database. Compares the configuration with the existing database schema and reports warnings.

src/en/guide/conf/dependencyResolution.gdoc

@@ -1,6 +1,6 @@
 Grails features a dependency resolution DSL that lets you control how plugins and JAR dependencies are resolved.
 
-You can choose to use Aether (since Grails 2.3) or Apache Ivy as the dependency resolution engine. Aether is the dependency resolution library used by the Maven build tool, so if you are looking for Maven-like behavior then Aether is the better choise. Ivy allows more flexibility if you wish to resolve jars from flat file systems or none HTTP repositories. Aether is the default dependency resolution engine for Grails applications since Grails 2.3.
+You can choose to use Aether (since Grails 2.3) or Apache Ivy as the dependency resolution engine. Aether is the dependency resolution library used by the Maven build tool, so if you are looking for Maven-like behavior then Aether is the better choice. Ivy allows more flexibility if you wish to resolve jars from flat file systems or none HTTP repositories. Aether is the default dependency resolution engine for Grails applications since Grails 2.3.
 
 {warning}
 As of Grails 2.4 the Ivy resolver is considered deprecated and no longer maintained. It is recommended all users switch to using Aether.

src/en/guide/conf/dependencyResolution/mavendeploy.gdoc

@@ -57,7 +57,7 @@ remoteRepository(id: "myRepo", url: "scp://localhost/www/repository") {
 }
 {code}
 
-By default the plugin will try to detect the protocol to use from the URL of the repository (ie "http" from "http://.." etc.), however to specify a different protocol you can do:
+By default the plugin will try to detect the protocol to use from the URL of the repository (e.g. "http" from "http://.." etc.), however to specify a different protocol you can do:
 
 {code}
 grails maven-deploy --repository=myRepo --protocol=webdav

src/en/guide/contributing.gdoc

@@ -1 +1 @@
-Grails is an open source project with an active community and we rely heavily on that community to help make Grails better. As such, there are various ways in which people can contribute to Grails. One of these is by [writing useful plugins|guide:plugins] and making them publicly available. In this chapter, we'll look at some fo the other options.
+Grails is an open source project with an active community and we rely heavily on that community to help make Grails better. As such, there are various ways in which people can contribute to Grails. One of these is by [writing useful plugins|guide:plugins] and making them publicly available. In this chapter, we'll look at some of the other options.

src/en/guide/contributing/build.gdoc

@@ -3,7 +3,7 @@ If you're interested in contributing fixes and features to the core framework, y
 * A JDK (1.6 or above)
 * A git client
 
-Once you have all the pre-requisite packages installed, the next step is to download the Grails source code, which is hosted at [GitHub|http://github.com] in several repositories owned by the ["grails" GitHub user|http://github.com/grails]. This is a simple case of cloning the repository you're interested in. For example, to getthe core framework run:
+Once you have all the pre-requisite packages installed, the next step is to download the Grails source code, which is hosted at [GitHub|http://github.com] in several repositories owned by the ["grails" GitHub user|http://github.com/grails]. This is a simple case of cloning the repository you're interested in. For example, to get the core framework run:
 
 {code}
 git clone http://github.com/grails/grails-core.git

src/en/guide/i18n.gdoc

@@ -4,4 +4,4 @@ Grails supports Internationalization (i18n) out of the box by leveraging the und
 A Locale object represents a specific geographical, political, or cultural region. An operation that requires a Locale to perform its task is called locale-sensitive and uses the Locale  to tailor information for the user. For example, displaying a number is a locale-sensitive operation--the number should be formatted according to the customs/conventions of the user's native country, region, or culture.
 {quote}
 
-A Locale is made up of a [language code|http://www.loc.gov/standards/iso639-2/php/English_list.php] and a [country code|http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm]. For example "en_US" is the code for US english, whilst "en_GB" is the code for British English.
+A Locale is made up of a [language code|http://www.loc.gov/standards/iso639-2/php/English_list.php] and a [country code|http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm]. For example "en_US" is the code for US English, whilst "en_GB" is the code for British English.

src/en/guide/introduction/whatsNew/persistenceFeatures.gdoc

@@ -29,7 +29,7 @@ h4. New findOrCreate and findOrSave Methods
 Domain classes have support for the findOrCreateWhere, findOrSaveWhere, findOrCreateBy and findOrSaveBy query methods which behave just like findWhere and findBy methods except that they should never return null. If a matching instance cannot be found in the database then a new instance is created, populated with values represented in the query parameters and returned. In the case of findOrSaveWhere and findOrSaveBy, the instance is saved before being returned.
 
 {code}
-def book = Book.findOrCreateWhere(author: 'Douglas Adams', title: "The Hitchiker's Guide To The Galaxy")
+def book = Book.findOrCreateWhere(author: 'Douglas Adams', title: "The Hitchhiker's Guide To The Galaxy")
 def book = Book.findOrSaveWhere(author: 'Daniel Suarez', title: 'Daemon')
 def book = Book.findOrCreateByAuthorAndTitle('Daniel Suarez', 'Daemon')
 def book = Book.findOrSaveByAuthorAndTitle('Daniel Suarez', 'Daemon')

src/en/guide/introduction/whatsNew22.gdoc

@@ -70,7 +70,7 @@ def c = Box.createCriteria()
 
 def results = c.list {
     projections {
-      sqlProjection '(2 * (width + height)) as perimiter, (width * height) as area', ['perimeter', 'area'], [INTEGER, INTEGER]
+      sqlProjection '(2 * (width + height)) as perimeter, (width * height) as area', ['perimeter', 'area'], [INTEGER, INTEGER]
     }
 }
 {code}

src/en/guide/introduction/whatsNew24.gdoc

@@ -26,8 +26,8 @@ The asset-pipeline provides a new, easier to manage, faster means of managing yo
 
 All your assets should now live in the @grails-app/assets@ subfolders. Three folders are made for you by default:
 
-* javascripts
-*  stylesheets
+* javascript
+* stylesheets
 * images
 
 Now, defining manifests are done directly in your JavaScript files, or CSS by using require directives!
@@ -226,7 +226,7 @@ This means that the Maven plugin version number is no longer tied to the version
 
 h4. Unit Testing improvements
 
-There is a Grails "unit testing runtime" that is based on the previous TestMixin based solution. It now separates the TestMixin classes and the actual runtime that handles the lifecycle of the Grails unit testing runtime. State of the runtime is not kept in static fields of the TestMixin classes anymore. The Groovy AST transformation behind the TestMixin annotation integrates to Junit and Spock test classes by adding Junit Rule fields to the class. In the previous solution, Before/BeforeClass and After/AfterClass annotations on AST added mix-in methods were used for the integration.
+There is a Grails "unit testing runtime" that is based on the previous TestMixin based solution. It now separates the TestMixin classes and the actual runtime that handles the lifecycle of the Grails unit testing runtime. State of the runtime is not kept in static fields of the TestMixin classes anymore. The Groovy AST transformation behind the TestMixin annotation integrates to JUnit and Spock test classes by adding JUnit Rule fields to the class. In the previous solution, Before/BeforeClass and After/AfterClass annotations on AST added mix-in methods were used for the integration.
 
 Some of the main features:
 

src/en/guide/plugins/evaluatingConventions.gdoc

@@ -34,7 +34,7 @@ The @GrailsClass@ interface has a number of useful methods that let you further
 * @getFullName@ - Returns the full name of the class in the application with the trailing convention part and with the package name
 * @getPropertyName@ - Returns the name of the class as a property name
 * @getLogicalPropertyName@ - Returns the logical property name of the class in the application without the trailing convention part if applicable
-* @getNaturalName@ - Returns the name of the property in natural terms (eg. 'lastName' becomes 'Last Name')
+* @getNaturalName@ - Returns the name of the property in natural terms (e.g. 'lastName' becomes 'Last Name')
 * @getPackageName@ - Returns the package name
 
 For a full reference refer to the [javadoc API|api:org.codehaus.groovy.grails.commons.GrailsClass].

src/en/guide/scaffolding.gdoc

@@ -13,7 +13,7 @@ As of Grails 2.3, the scaffolding feature has been moved to a plugin. By default
     }
 {code}
 
-Version 1.0.0 of the plugin provides the same scaffolding seen in Grails 2.2.x and below. Version 2.0.x of the scaffolding plugin includes different scaffolding templates that are aligned with the new REST APIs introcued in Grails 2.3 and above.
+Version 1.0.0 of the plugin provides the same scaffolding seen in Grails 2.2.x and below. Version 2.0.x of the scaffolding plugin includes different scaffolding templates that are aligned with the new REST APIs introduced in Grails 2.3 and above.
 
 h4. Dynamic Scaffolding
 

src/en/guide/security/codecs.gdoc

@@ -58,7 +58,7 @@ Example of usage:
 Note that the HTML encoding does not re-encode apostrophe/single quote so you must use double quotes on attribute values to avoid text with apostrophes affecting your page.
 {note}
 
-HTMLCodec defaults to HTML4 style escaping (legacy HTMLCodec implementation in Grails ersions before 2.3.0 ) which escapes non-ascii characters. 
+HTMLCodec defaults to HTML4 style escaping (legacy HTMLCodec implementation in Grails versions before 2.3.0) which escapes non-ascii characters. 
 
 You can use plain XML escaping instead of HTML4 escaping by setting this config property in Config.groovy:
 {code}

src/en/guide/security/securingAgainstAttacks.gdoc

@@ -8,7 +8,7 @@ def vulnerable() {
 }
 {code}
 
-or the analagous call using a GString:
+or the analogous call using a GString:
 
 {code:java}
 def vulnerable() {

src/en/guide/spring/theBeanBuilderDSLExplained.gdoc

@@ -111,7 +111,7 @@ Here the example property of @AnotherBean@ is set using a runtime reference to t
 
 {code:java}
 ApplicationContext parent = ...//
-der bb = new BeanBuilder(parent)
+def bb = new BeanBuilder(parent)
 bb.beans {
     anotherBean(AnotherBean) {
         example = ref("${beanName}Bean", true)