diff --git a/docs/topics/deploy.rst b/docs/topics/deploy.rst index b7394d5ce..bc48ddce7 100644 --- a/docs/topics/deploy.rst +++ b/docs/topics/deploy.rst @@ -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: diff --git a/docs/topics/firebug.rst b/docs/topics/firebug.rst index 359c99450..b93ee4ff9 100644 --- a/docs/topics/firebug.rst +++ b/docs/topics/firebug.rst @@ -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 diff --git a/docs/topics/shell.rst b/docs/topics/shell.rst index 9c9411d6d..83a5a378d 100644 --- a/docs/topics/shell.rst +++ b/docs/topics/shell.rst @@ -56,7 +56,7 @@ Available Shortcuts * ``view(response)`` - open the given response in your local web browser, for inspection. This will add a `\ 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. .. _ tag: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base