fix typos & reword faq.rst
update * personnaly ==> personally * reword "jQuery being available on every page" * update "never really" ==> "never"
Showing
1 changed file
with
3 additions
and
3 deletions
... | @@ -63,7 +63,7 @@ Also, don't forget that CasperJS supports a `CommonJS-compliant module pattern < | ... | @@ -63,7 +63,7 @@ Also, don't forget that CasperJS supports a `CommonJS-compliant module pattern < |
63 | 63 | ||
64 | .. note:: | 64 | .. note:: |
65 | 65 | ||
66 | CasperJS' implementation of ``require()`` differs a bit from the one provided by PhantomJS_, but I personnaly never really encountered any functional difference. | 66 | CasperJS' implementation of ``require()`` differs a bit from the one provided by PhantomJS_, but I personally never encountered any functional difference. |
67 | 67 | ||
68 | 68 | ||
69 | .. index:: Versionning | 69 | .. index:: Versionning |
... | @@ -97,7 +97,7 @@ A first solution is to inject it into the remote DOM environment by hand using t | ... | @@ -97,7 +97,7 @@ A first solution is to inject it into the remote DOM environment by hand using t |
97 | 97 | ||
98 | casper.page.injectJs('/path/to/jquery.js'); | 98 | casper.page.injectJs('/path/to/jquery.js'); |
99 | 99 | ||
100 | If you need jQuery being available everytime, you can also make it being injected in every received response by setting the ``clientScripts`` option of CasperJS:: | 100 | In the event that you require jQuery being available on every page, you can make use of the ``clientScripts`` option of CasperJS:: |
101 | 101 | ||
102 | var casper = require('casper').create({ | 102 | var casper = require('casper').create({ |
103 | clientScripts: ["includes/jquery.min.js"] | 103 | clientScripts: ["includes/jquery.min.js"] |
... | @@ -189,7 +189,7 @@ Nowhere. CasperJS doesn't write logs on the filesystem. You have to implement th | ... | @@ -189,7 +189,7 @@ Nowhere. CasperJS doesn't write logs on the filesystem. You have to implement th |
189 | What's this mysterious ``__utils__`` object? | 189 | What's this mysterious ``__utils__`` object? |
190 | -------------------------------------------- | 190 | -------------------------------------------- |
191 | 191 | ||
192 | The ``__utils__`` object is actually a :ref:`ClientUtils object <clientutils_prototype>` which have been automatically injected into the page DOM and is therefore alway available. | 192 | The ``__utils__`` object is actually a :ref:`ClientUtils object <clientutils_prototype>` which have been automatically injected into the page DOM and is therefore always available. |
193 | 193 | ||
194 | So everytime to perform an :ref:`evaluate() <casper_evaluate>` call, you have this instance available to perform common operation like: | 194 | So everytime to perform an :ref:`evaluate() <casper_evaluate>` call, you have this instance available to perform common operation like: |
195 | 195 | ... | ... |
-
Please register or sign in to post a comment