From 475766c73a4fd6f65caa5c5c25e713eab8eac84b Mon Sep 17 00:00:00 2001
From: Peter Bronez <pbronez@deepmile.com>
Date: Thu, 26 Mar 2015 15:34:30 -0400
Subject: [PATCH] Converted sel.xpath() calls to response.xpath() in Extracting
 the data

---
 docs/intro/tutorial.rst | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/intro/tutorial.rst b/docs/intro/tutorial.rst
index ad808316b..286a591ee 100644
--- a/docs/intro/tutorial.rst
+++ b/docs/intro/tutorial.rst
@@ -315,19 +315,19 @@ is inside a ``<ul>`` element, in fact the *second* ``<ul>`` element.
 So we can select each ``<li>`` element belonging to the sites list with this
 code::
 
-    sel.xpath('//ul/li')
+    response.xpath('//ul/li')
 
 And from them, the sites descriptions::
 
-    sel.xpath('//ul/li/text()').extract()
+    response.xpath('//ul/li/text()').extract()
 
 The sites titles::
 
-    sel.xpath('//ul/li/a/text()').extract()
+    response.xpath('//ul/li/a/text()').extract()
 
 And the sites links::
 
-    sel.xpath('//ul/li/a/@href').extract()
+    response.xpath('//ul/li/a/@href').extract()
 
 As we've said before, each ``.xpath()`` call returns a list of selectors, so we can
 concatenate further ``.xpath()`` calls to dig deeper into a node. We are going to use