From 36907daf461ae64e09a6de004e1f80c7e4daefec Mon Sep 17 00:00:00 2001
From: Derek Jones <derek.jones@ellislab.com>
Date: Wed, 5 Oct 2011 15:12:27 -0500
Subject: fixed code blocks in at_a_glance (finishes overview folder code block
 cleanup)

---
 user_guide_src/source/overview/at_a_glance.rst | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

(limited to 'user_guide_src/source/overview/at_a_glance.rst')

diff --git a/user_guide_src/source/overview/at_a_glance.rst b/user_guide_src/source/overview/at_a_glance.rst
index df4e3ca06..31f0b4dd9 100644
--- a/user_guide_src/source/overview/at_a_glance.rst
+++ b/user_guide_src/source/overview/at_a_glance.rst
@@ -80,11 +80,19 @@ simply can not match the performance of native PHP, and the syntax that
 must be learned to use a template engine is usually only marginally
 easier than learning the basics of PHP. Consider this block of PHP code::
 
-	<ul>  <?php foreach ($addressbook as $name):?>  <li><?=$name?></li>  <?php endforeach; ?>  </ul>
+	<ul>
+	<?php foreach ($addressbook as $name):?>
+		<li><?=$name?></li>
+	<?php endforeach; ?>
+	</ul>
 
 Contrast this with the pseudo-code used by a template engine::
 
-	<ul>  {foreach from=$addressbook item="name"}  <li>{$name}</li>  {/foreach}  </ul>
+	<ul>
+	{foreach from=$addressbook item="name"}
+		<li>{$name}</li>
+	{/foreach}
+	</ul>
 
 Yes, the template engine example is a bit cleaner, but it comes at the
 price of performance, as the pseudo-code must be converted back into PHP
-- 
cgit v1.2.3-24-g4f1b