Fix typo and added more info

GSoC2011GUIOverhaul.wiki

diff --git a/GSoC2011GUIOverhaul.wiki b/GSoC2011GUIOverhaul.wiki
index f0ea3d0..c467c02 100644
--- a/GSoC2011GUIOverhaul.wiki
+++ b/GSoC2011GUIOverhaul.wiki
@@ -28,7 +28,7 @@
 
 Iconic dashboard basically is a chunk of template, or a Django view that will be rendered as a partial HTML. Specifically, the view will be rendered as a collection of links that either nested (link to another block/div in the same page) or linked to another page. Iconic dashboard consists of:
  * Django view (app/soc/views/dashboard.py). Classes in this view are not supposed to be instantiated directly, where each class acts as a base class. To implement iconic dashboard at least one derived class must be created.
- * Djano template (app/soc/templates/v2/soc/dashboard/*)
+ * Django template (app/soc/templates/v2/soc/dashboard/*)
 
 Don't be confused with a dashboard page (participant dashboard and admin dashboard) and the iconic dashboard itself. To avoid the confusion, let's say iconic dashboard is a helper in form of view and template that used by dashboard page, such as participant dashboard and admin dashboard in gsoc module.
 
@@ -43,13 +43,14 @@
    * *"B-1"* with description *"List of my todos"* and links to a dashboard where my todos will be listed in.
    * *"B-2"* with description *"List of my todos"* and links to a dashboard where my todos will be listed in.
 
-In iconic dashboard implementation, *"A"* and *"B"* considered as both links and dashboard (because *"A"* and *"B"* have children, hence it acts as dashboard/container for their children). The root/main dashboard must be defined in the view to act as a container for both *"A"* and *"B"*, let's name it *MainDashboard*. This is not a must, but it will make life easier later if we name a dashboard class with "Dashboard" suffix. From our requirements aboove, there are five dashboards:
+In iconic dashboard implementation, both *"A"* and *"B"* are considered as link and dashboard (because *"A"* and *"B"* have children, hence it acts as dashboard/container for their children). The root/main dashboard must be defined in the view to act as a container for both *"A"* and *"B"*, let's name it *MainDashboard*. This is not a must, but it will make life easier later if we name a dashboard class with "Dashboard" suffix. From our requirements aboove, there are five dashboards, eh six with the *MainDashboard*:
 
- # DashboardA(Dashboard)
-   # DashboardA2(Dashboard)
- # DashboardB(Dashboard)
-   # DashboardB1(Dashboard)
-   # DashboardB1(Dashboard)
+ * MainDashboard
+   # DashboardA(Dashboard)
+     # DashboardA2(Dashboard)
+   # DashboardB(Dashboard)
+     # DashboardB1(Dashboard)
+     # DashboardB1(Dashboard)
 
 *"B-1"* and *"B-1"* have no child, but they contain list. So either it has children or list, declare it as a dashboard. All classes must be derived from Dashboard. To import the base class of dashboard: