This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
I've made a few small corrections, some spelling changes and typo fixes.
I've tried to respect regional spelling differences and avoided proposing hyphenating compound words.
Please enter the commit message for your changes. Lines starting
Loading branch information
3 changed files
and 3 deletions.
@@ -8,7 +8,7 @@ This section describes the different options you have for deploying your Scrapy
spiders to run them on a regular basis. Running Scrapy spiders in your local
machine is very convenient for the (early) development stage, but not so much
when you need to execute long-running spiders or move spiders to run in
production continously. This is where the solutions for deploying Scrapy
production continuously. This is where the solutions for deploying Scrapy
spiders come in.
Popular choices for deploying Scrapy spiders are:
@@ -118,7 +118,7 @@ they work as we expect.
As you can see, the page markup is not very descriptive: the elements don't
contain ``id``, ``class`` or any attribute that clearly identifies them, so
we' 'll use the ranking bars as a reference point to select the data to extract
we'll use the ranking bars as a reference point to select the data to extract
when we construct our XPaths.
After using FireBug, we can see that each link is inside a ``td`` tag, which is
@@ -56,7 +56,7 @@ Available Shortcuts
* ``view(response)`` - open the given response in your local web browser, for
inspection. This will add a ` \<base\> tag`_ to the response body in order
for external links (such as images and style sheets) to display properly.
Note, however,that this will create a temporary file in your computer,
Note, however, that this will create a temporary file in your computer,
which won't be removed automatically.
.. _<base> tag: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base