Permalink
Browse files

Corrected some spelling mistakes in the docs.

  • Loading branch information...
1 parent d262a56 commit 474acb720470393c34427f49e7229c874ef3f04a @emarthinsen emarthinsen committed Apr 2, 2012
@@ -32,7 +32,7 @@ var casper = require('casper').create({
## Casper options
-All the available options are detailled below:
+All the available options are detailed below:
<table class="table table-striped table-condensed" caption="Casper options">
<thead>
@@ -79,7 +79,7 @@ All the available options are detailled below:
<td><code>"error"</code></td>
<td>
Logging level (see the <a href="#logging">logging
- section</a> for more informations)
+ section</a> for more information)
</td>
</tr>
<tr>
@@ -292,7 +292,7 @@ Also have a look at [`Casper.forward()`](#phantom_Casper_forward).
<h3 id="phantom_Casper_base64encode"><code>Casper#base64encode(String url [, String method, Object data])</code></h3>
-Encodes a resource using the base64 algorithm synchroneously using
+Encodes a resource using the base64 algorithm synchronously using
client-side XMLHttpRequest.
<span class="label label-info">Note</span> We cannot use `window.btoa()`
@@ -516,7 +516,7 @@ sample script for concrete usecase.
<h3 id="phantom_Casper_echo"><code>Casper#echo(String message[, String style])</code></h3>
-Prints something to stdout, optionnaly with some fancy color (see the
+Prints something to stdout, optionally with some fancy color (see the
[`Colorizer`](#colorizer) section of this document for more
information).
@@ -639,7 +639,7 @@ casper.run();
<h3 id="phantom_Casper_fill"><code>Casper#fill(String selector, Object values[, Boolean submit])</code></h3>
-Fills the fields of a form with given values and optionnaly submit it.
+Fills the fields of a form with given values and optionally submits it.
Example with this sample html form:
@@ -846,7 +846,7 @@ casper.run();
```
`Casper.run()` also accepts an `onComplete` callback, which you can
-consider as a custom final step to perform when all te other steps has
+consider as a custom final step to perform when all the other steps have
been executed. Just don't forget to `exit()` Casper if you define one!
```javascript
@@ -895,7 +895,7 @@ casper.run();
<h3 id="phantom_Casper_start"><code>Casper#start(String url[, function then])</code></h3>
Configures and starts Casper, then open the provided `url` and
-optionnaly adds the step provided by the `then` argument.
+optionally adds the step provided by the `then` argument.
**Example:**
@@ -990,7 +990,7 @@ casper.run();
<h3 id="phantom_Casper_thenOpen"><code>Casper#thenOpen(String location[, function then])</code></h3>
-Adds a new navigation step for opening a new location, and optionnaly
+Adds a new navigation step for opening a new location, and optionally
add a next step when its loaded.
**Example:**
@@ -1063,7 +1063,7 @@ casper.start('http://google.com/', function() {
<h3 id="phantom_Casper_wait"><code>Casper#wait(Number timeout[, Function then])</code></h3>
-Pause steps suite execution for a given amount of time, and optionnaly
+Pause steps suite execution for a given amount of time, and optionally
execute a step on done.
**Example:**
@@ -1,9 +1,9 @@
-CasperJS ships with a builting command line parser on top of PhantomJS'
+CasperJS ships with a built-in command line parser on top of PhantomJS'
one, located in the `cli` module; it exposes passed arguments as
**positional ones** and **named options**
But no worries for manipulating the `cli` module parsing API, a `Casper`
-instance always contains a rady to use `cli` property, allowing easy
+instance always contains a ready to use `cli` property, allowing easy
access of all these parameters.
Let's consider this simple casper script:
@@ -86,7 +86,7 @@ if (casper.cli.args.length === 0 && Object.keys(casper.cli.options).length === 0
```
Last but not least, you can still use all PhantomJS standard CLI options
-as you would do with any other phantomjs script. To remeber what they
+as you would do with any other phantomjs script. To remember what they
are, just run the `casperjs --help` command:
```
@@ -110,4 +110,4 @@ Options:
--proxy=address:port Sets the network proxy (e.g. "--proxy=192.168.1.42:8080")
--script-encoding Sets the encoding used for the starting script (default is 'utf8')
--version Prints out CasperJS version
-```
+```
@@ -1,4 +1,4 @@
-Casper ships with a few client-side utilitites which are injected in the
+Casper ships with a few client-side utilities which are injected in the
remote DOM environment, and accessible from there through the
`__utils__` object instance of the `ClientUtils` class of the
`clientutils` module.
@@ -1,4 +1,4 @@
-Here's a selection of the most frequesntly asked questions by casperjs
+Here's a selection of the most frequently asked questions by casperjs
newcomers.
<h2 id="faq-help">I'm stuck! What can I do?</h2>
@@ -41,7 +41,7 @@ I cannot do much to make the situation really better, unfortunately :/
Sure, as every single other javascript library on Earth.
-A first solution is to inject it into the remote DOM environement by
+A first solution is to inject it into the remote DOM environment by
hand using the standard `WebPage.injectJs()` method:
casper.page.injectJs('http://code.jquery.com/jquery-1.7.min.js');
@@ -2,7 +2,7 @@ CasperJS provides an [event handler](#events) very similar to the
[one](https://github.com/joyent/node/blob/master/lib/events.js) shipping
with [nodejs](http://nodejs.org); actually it borrows most of its
codebase. CasperJS also adds [*filters*](#filters), which are basically
-ways to alter values asynchroneously.
+ways to alter values asynchronously.
* * * * *
@@ -72,14 +72,14 @@ parameters passed to their callback:
<tr>
<td><code>http.auth</code></td>
<td><code>username, password</code></td>
- <td>Emitted when http autthentification parameters are set.</td>
+ <td>Emitted when http authentication parameters are set.</td>
</tr>
<tr>
<td><code>http.status.[code]</code></td>
<td><code>resource</code></td>
<td>
<p>
- Emitted when ny given HTTP reponse is received with the status code
+ Emitted when any given HTTP reponse is received with the status code
specified by <code>[code]</code>, eg.:
</p>
<pre class="prettyprint">casper.on('http.status.404', function(resource) {
@@ -184,7 +184,7 @@ parameters passed to their callback:
<tr>
<td><code>run.complete</code></td>
<td>None</td>
- <td>Emitted when the whole serie of steps in the stack have been executed.</td>
+ <td>Emitted when the whole series of steps in the stack have been executed.</td>
</tr>
<tr>
<td><code>run.start</code></td>
@@ -283,8 +283,8 @@ method:
<h2 id="filters">Filters</h2>
-Filters allow to alter some value asynchroneously. Sounds obscure? Let's
-take a simple example and let's imagine you would like to alter every
+Filters allow you to alter some values asynchronously. Sounds obscure? Let's
+take a simple example and imagine you would like to alter every
single url opened by CasperJS to append a `foo=42` query string
parameter:
@@ -294,7 +294,7 @@ parameter:
return /\?+/.test(location) ? location += "&foo=42" : location += "?foo=42";
});
-There you have it, every single requested url will have these appended.
+There you have it, every single requested url will have this appended.
Let me bet you'll find far more interesting use cases than my silly one
;)
@@ -228,8 +228,7 @@ casper.test.pass("Barrack Obama");
<h3 id="phantom_Casper_Tester_renderResults"><code>Tester#renderResults(Boolean exit, Number status, String save)</code></h3>
-Render tests results, an optionnaly exit phantomjs and saves results in
-a XUnit formatted file.
+Render tests results, save results in an XUnit formatted file, and optionally exit phantomjs.
```javascript
var casper = require('casper').create();
@@ -52,7 +52,7 @@ following:
### Exporting results in *xUnit* format
CasperJS can export the results of the test suite to an xUnit XML file,
-which is compatible with continous integration tools such as
+which is compatible with continuous integration tools such as
[Jenkins](http://jenkins-ci.org/). To save the xUnit log of your test
suite to a `log.xml` file, you can process this way:
@@ -95,13 +95,13 @@ $ casperjs test tests/suites
### Organizing your tests
Of course writing all your tests in a single file may be painful, so you
-can split them accross files.
+can split them across files.
<div class="alert-message block-message">
<p>
<span class="label label-important">Important</span>
There are <strong>two important conditions</strong> for splitting
- your test suite accross several files:
+ your test suite across several files:
</p>
<ol class="bottom">
<li>
View
@@ -85,7 +85,7 @@
<div class="page-header">
<h1>
Events &amp; filters
- <small>hooking &amp; altering CasperJS environement at runtime</small>
+ <small>hooking &amp; altering thr CasperJS environment at runtime</small>
</h1>
</div>
<div id="filters_contents"></div>

0 comments on commit 474acb7

Please sign in to comment.