summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPuneeth Chaganti2011-07-28 16:02:44 +0530
committerPuneeth Chaganti2011-07-28 16:02:44 +0530
commit4eab74bbc36f7647ebf77e4350bb55a225d75c24 (patch)
tree76d7c6b4a49fb156aee25078cce838b760a1a66f
parentc5321b16ea571bb2cc1e0a0953b73a641de34c4a (diff)
downloadst-scripts-4eab74bbc36f7647ebf77e4350bb55a225d75c24.tar.gz
st-scripts-4eab74bbc36f7647ebf77e4350bb55a225d75c24.tar.bz2
st-scripts-4eab74bbc36f7647ebf77e4350bb55a225d75c24.zip
Fix getting_started_with_for/script.rst for 2-column format.
-rw-r--r--getting_started_with_for/script.rst7
1 files changed, 3 insertions, 4 deletions
diff --git a/getting_started_with_for/script.rst b/getting_started_with_for/script.rst
index c3eecc1..ad7f0a6 100644
--- a/getting_started_with_for/script.rst
+++ b/getting_started_with_for/script.rst
@@ -67,10 +67,9 @@ tutorial on "Getting started with Lists".
In Python whitespace is significant, and the blocks are visually
separated.The best practice is to indent the code using four spaces.
-As you can see in the slide, “Block B” is an inner block, indented by
-4 spaces.
-After “Block B” the next statement in ”Block A” starts from the same
-indentation level of other ”Block A” Statements.
+As you can see in the slide, "Block B" is an inner block, indented by
+4 spaces. After "Block B" the next statement in "Block A" starts from
+the same indentation level of other "Block A" Statements.
.. R4