Skip to content

Commit

Permalink
Merge pull request #22 from Digenis/doc-scrapy_references
Browse files Browse the repository at this point in the history
Substitute 3 leftover "Scrapy" references in doc
  • Loading branch information
kmike committed Oct 13, 2015
2 parents 5894076 + ad89145 commit d745477
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -249,7 +249,7 @@ XPath specification.
Using EXSLT extensions
----------------------

Being built atop `lxml`_, Scrapy selectors also support some `EXSLT`_ extensions
Being built atop `lxml`_, parsel selectors support some `EXSLT`_ extensions
and come with these pre-registered namespaces to use in XPath expressions:


Expand Down Expand Up @@ -502,7 +502,7 @@ other classes, and if you just use ``contains(@class, 'someclass')`` to make up
for that you may end up with more elements that you want, if they have a different
class name that shares the string ``someclass``.

As it turns out, Scrapy selectors allow you to chain selectors, so most of the time
As it turns out, parsel selectors allow you to chain selectors, so most of the time
you can just select by class using CSS and then switch to XPath when needed::

>>> from parsel import Selector
Expand Down Expand Up @@ -618,8 +618,8 @@ instead of having to call it manually, this is because of two reasons, which, in
of relevance, are:

1. Removing namespaces requires to iterate and modify all nodes in the
document, which is a reasonably expensive operation to perform for all
documents crawled by Scrapy
document, which is a reasonably expensive operation to perform by default
for all documents.

2. There could be some cases where using namespaces is actually required, in
case some element names clash between namespaces. These cases are very rare
Expand Down

0 comments on commit d745477

Please sign in to comment.