diff options
| author | Jovina | 2011-07-28 17:03:04 +0530 |
|---|---|---|
| committer | Jovina | 2011-07-28 17:03:04 +0530 |
| commit | 68f3741c2fd2acc79089ffaaa88e85632e0ba23b (patch) | |
| tree | 364e823275e51c298db53391465ddef1005b9a23 /getting_started_with_for | |
| parent | a967e341eaf683b27c92b5e4817cb62f3f14e572 (diff) | |
| parent | cc476c4e86346ca0d92e72cd84efb7d3e90069ac (diff) | |
| download | st-scripts-68f3741c2fd2acc79089ffaaa88e85632e0ba23b.tar.gz st-scripts-68f3741c2fd2acc79089ffaaa88e85632e0ba23b.tar.bz2 st-scripts-68f3741c2fd2acc79089ffaaa88e85632e0ba23b.zip | |
Merge branch 'master' of https://github.com/FOSSEE/st-scripts
Diffstat (limited to 'getting_started_with_for')
| -rw-r--r-- | getting_started_with_for/script.rst | 7 |
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 |