changes done

pages/DesignTips.html

@@ -9,9 +9,9 @@ <h2>
   <p>
     One of Oppia's strengths is its ability to bring interactivity and
     <a href="https://teachingcommons.stanford.edu/resources/learning/learning-activities/guided-discovery-problems">
-      guided discovery learning
+      guide towards discovery learning
     </a>
-    to online, computer-based learning. Thus, a common format for an Oppia exploration is to pose a problem to the reader and guide them towards
+    In online, computer-based learning. Thus, a common format for an Oppia exploration is to pose a problem to the reader and guide them towards
     solving this problem by posing a series of questions. This way, the reader
     actively discovers the answer with the exploration's help, as opposed to
     just being told what the answer is.
@@ -28,7 +28,7 @@ <h2>
     Once you have a clear idea of what concept your exploration is trying to
     teach, it's usually easiest to start by coming up with a single series of
     questions and answers that might help a student understand this concept.
-    These will form the "critical path" of your exploration -- the trunk on
+    These will form the "critical path" of your exploration -- The trunk on
     which all the other branches will depend. It doesn't really matter what
     this path is, as long as it goes all the way from start to finish.
   </p>
@@ -73,7 +73,7 @@ <h3>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Common misconceptions
+    Common Misconceptions
   </h3>
 
   <p>
@@ -107,14 +107,14 @@ <h3>
     <a id="Loopbacks" class="anchor" href="#Loopbacks" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Loopbacks
+  Loop-backs
   </h3>
 
   <p>
     Another way to deal with wrong answers is to simply loop back and ask the
     question again. But for this to be beneficial and educational, you must
     tell the student what was wrong with their answer. Therefore, when using
-    loopbacks like this, you should classify the possible wrong answers in as
+    loop-backs like this, you should classify the possible wrong answers in as
     much detail as possible, and provide detailed feedback on why a particular
     answer was wrong. (It might also be a good idea to mix and match: loop the
     student back to the question for simple mistakes, but take them on a longer
@@ -124,7 +124,7 @@ <h3>
 
   <p>
     There are some considerations and issues to watch out for when using
-    loopbacks:
+    loop-backs:
   </p>
   <ul>
     <li>
@@ -149,7 +149,7 @@ <h3>
       an answer to the original question.
     </li>
     <li>
-      <strong>Don't</strong> use loopbacks for incorrect text-field answers (or
+      <strong>Don't</strong> use loop-backs for incorrect text-field answers (or
       other free-form classifiers). Avoid situations where there's just one
       "correct" answer that moves you along, but lots of wrong answers that
       make you loop back and guess again. Having to read the exploration
@@ -158,7 +158,7 @@ <h3>
   </ul>
 
   <p>
-    A good rule of thumb for whether you should use loopbacks is whether you
+    A good rule of thumb for whether you should use loop-backs is whether you
     can separate all the possible "wrong" answers into large groups, for which
     you can provide explicit helpful feedback that gives the reader more
     information. If not, you may be better off branching into a longer
@@ -229,7 +229,7 @@ <h3>
       Students can sometimes get confused and lost if the question is too broad
       or open-ended, because they are unsure of what exactly is expected of
       them. They may just say "I don't know". In that case, the exploration can
-      simply go on with a detailed guided walkthrough of the topics involved.
+      simply go on with a detailed guided walk-through of the topics involved.
       If you use a broad question like this, try to make it clear that there's
       no one right (or wrong) answer; you're just looking for ideas. Or, if you
       have a specific type of answer in mind, be as explicit as possible about
@@ -325,7 +325,7 @@ <h2>
     Parameter-based design patterns
   </h2>
   <p>
-    Oppia's parameter functionality enables a number of interesting design
+    Oppia's parameter functionality enables a number of interesting design and
     patterns. <a href="#Parameters">Here</a> is a more detailed guide to using
     parameters, with examples.
   </p>
@@ -335,7 +335,7 @@ <h3>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Randomized questions
+    Randomized Questions
   </h3>
   <p>
     It's easy to create a randomized parameter that takes one of several
@@ -348,7 +348,7 @@ <h3>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Making content dynamic
+    Making Content Dynamic
   </h3>
   <p>
     Often, when a student returns to a card they already visited, the original
@@ -359,7 +359,7 @@ <h3>
 
     <tt>
       <code>
-        {{if redux == "1" then "'So, how do you think he does it?' asks your friend." else "Ah, so where were we again?"}}
+        {{if redux == "1" then "'So, how do you think he does it?' asks your friends." else "Ah, so where were we again?"}}
       </code>
     </tt>
 
@@ -385,7 +385,7 @@ <h3>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Parameterized feedback
+    Parameterized Feedback
   </h3>
   <p>
     Sometimes it's useful to use parameters in the feedback you give to the
@@ -406,7 +406,7 @@ <h3>
     Echoing back the answer
   </h3>
   <p>
-    Even if your exploration is not mathematical, it can be useful to echo back
+    Even if your exploration is not mathematical, it can be useful to Echoing_back_to
     the student's answer either immediately ("Oh, so you think that
     <code>{{answer}}</code>?") or later on ("I think you said that your
     favorite color was <code>{{color}}</code>?"). For the latter case, you'd

pages/DownloadingAnExploration.html

@@ -4,7 +4,7 @@ <h2>
        href="#Downloading_Explorations" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Downloading an Exploration
+    Downloading An Exploration
   </h2>
 
   <p>

pages/EmbeddingAnExploration.html

@@ -3,7 +3,7 @@ <h2>
     <a id="embedded" class="anchor" href="#embedded" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Embedding an Exploration
+    Embedding An Exploration
   </h2>
 
   <p>
@@ -26,15 +26,15 @@ <h3>
     <a id="Step_1:_Include_the_embedding_script" class="anchor" href="#Step_1:_Include_the_embedding_script" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Step 1: Include the embedding script
+    Step 1: Include The Embedding Script
   </h3>
 
   <p>
     Option 1: Use one of the hosted scripts, by including one of the following codes on your page:
   </p>
 
   <ul>
-    <li>jsDelivr:</li>
+    <li>Js-Deliver:</li>
     <pre class="prettyprint"><span class="tag">&lt;script</span><span class="pln"> </span><span class="atn">src</span><span class="pun">=</span><span class="atv">"//cdn.jsdelivr.net/gh/oppia/[email protected]/assets/scripts/oppia-player-0.0.3.min.js"</span><span class="tag">&gt;&lt;/script&gt;</span></pre>
     <li>CDNjs: </li>
     <pre class="prettyprint"><span class="pln">&nbsp; </span><span class="tag">&lt;script</span><span class="pln"> </span><span class="atn">src</span><span class="pun">=</span><span class="atv">"//cdnjs.cloudflare.com/ajax/libs/oppia/0.0.3/oppia-player.min.js"</span><span class="tag">&gt;&lt;/script&gt;</span>
@@ -70,18 +70,18 @@ <h3>
   <p>The meanings of the various attributes are as follows:</p>
   <ul>
     <li>
-      <tt>oppia-id</tt>: the id of the exploration (which you can find in the
+      <tt>oppia-id</tt>: The id of the exploration (which you can find in the
       exploration URL; it's the string of random characters between /create/
       and #/gui/).
     </li>
     <li>
-      <tt>src</tt>: the domain that hosts the exploration. If you are embedding
+      <tt>src</tt>: The domain that hosts the exploration. If you are embedding
       an exploration from oppia.org, this will be <tt>https://www.oppia.org</tt>.
       If you have set up your own instance of Oppia, use the corresponding domain
       name for that instance instead.
     </li>
     <li>
-      <tt>exploration-version</tt>: this is optional. If it is not specified,
+      <tt>Exploration-version</tt>: this is optional. If it is not specified,
       the latest version of the exploration will be embedded. If it is
       specified, it represents the version number of the exploration that you
       want to embed; you can determine this by looking at the History tab on
@@ -106,23 +106,23 @@ <h3>
     <a href="http://webmasters.stackexchange.com/questions/8525/how-to-open-the-javascript-console-in-different-browsers" rel="nofollow">
       development console
     </a>
-    in your browser, and check to see if there are any errors.
+    In your browser, and check to see if there are any errors.
   </p>
 
   <h2>
     <a id="advanced_options" class="anchor" href="#advanced_options"
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Advanced option
+    Advanced Option
   </h2>
 
   <h3>
     <a id="Integration_with_particular_platforms" class="anchor"
        href="#Integration_with_particular_platforms" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Integration with particular platforms
+    Integration With Particular Platforms
   </h3>
 
   <p>
@@ -131,7 +131,7 @@ <h3>
     the <tt>integrations</tt> subdirectory of the
     <a href="https://github.com/oppia/oppia/tree/develop/integrations_dev"
        rel="nofollow">
-      Oppia source code
+      Oppia Source Code
     </a>.
   </p>
 
@@ -140,7 +140,7 @@ <h3>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Event hooks (optional)
+    Event Hooks (optional)
   </h3>
 
   <p>

pages/ImprovingAnExploration.html

@@ -13,7 +13,7 @@ <h2>
   <p>
     If you want to improve an exploration, one starting point is to take a look
     at the answers that readers submitted. To view these, click on the
-    "Exploration Stats" tab in the exploration editor. If any reader has viewed
+    "Exploration Status" tab in the exploration editor. If any reader has viewed
     your exploration, you should see a page like this one:
   </p>
   <p><img src="static/images/analytics.png" width="100%" alt="An Analytics page comprising a horizontal 'completion rate' meter, depicting 'completions' in green and 'non completions' in red. This is followed by a flowchart depicting common paths learners have followed, from start to finish."></p>

pages/Parameters.html

@@ -13,10 +13,10 @@ <h2>
     done or seen. For example, in an earlier part of the exploration, the
     learner may have encountered a question which uses the number 164. If you
     want to use this information in another card, you can define a parameter
-    <tt>x</tt> to be 164, and in the second card you can refer to <tt>x</tt> to
+    <tt>X</tt> to be 164, and in the second card you can refer to <tt>X</tt> to
     get the value used in the earlier card. Note that this information is not
     associated with the learner in the long term, and is only maintained within
-    the context of a single exploration playthrough.
+    the context of a single exploration Play-through.
   </p>
 
   <p>
@@ -29,7 +29,7 @@ <h2>
   <ul>
     <li>Remembering the learner's name</li>
     <li>
-      Randomizing a question by picking a different value in each playthrough
+      Randomizing a question by picking a different value in each Play-through
     </li>
     <li>Keeping track of things the learner has done or seen already</li>
   </ul>
@@ -38,7 +38,7 @@ <h2>
     <a id="Enabling_parameters" class="anchor" href="#Enabling_parameters" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Enabling parameters
+    Enabling Parameters
   </h2>
 
   <p>
@@ -51,7 +51,7 @@ <h2>
     <a id="Special_parameter:_&quot;answer&quot;" class="anchor" href="#Special_parameter:_&quot;answer&quot;" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Special parameter: "answer"
+    Special parameter: "Answer"
   </h2>
 
   <p>
@@ -82,7 +82,7 @@ <h2>
     <li>
       <tt><code>{{a}}</code></tt>
       <ul>
-        <li>Returns the value of parameter a.</li>
+        <li>Returns the value of parameter a:</li>
       </ul>
     </li>
 
@@ -213,7 +213,7 @@ <h3>
     Remembering the learner's name
   </h3>
   <p>
-    You can make a card that asks the learner for her name, and that takes a
+    You can make a card that asks the learner for her/his name, and that takes a
     text answer. In the following card, the <tt><code>{{answer}}</code></tt>
     parameter will hold the user's name, since this would be the last answer
     entered. You could create a parameter change at the start of this card that
@@ -265,7 +265,7 @@ <h3>
     <a id="Counting_tries" class="anchor" href="#Counting_tries" aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Counting tries
+    Counting Tries
   </h3>
   <p>
     You can use a parameter to keep track of the number of times the learner

pages/PlanningAnExploration.html

@@ -4,7 +4,7 @@ <h2>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    Planning an Exploration
+    Planning An Exploration
   </h2>
 
   <p>
@@ -54,7 +54,7 @@ <h2>
        aria-hidden="true">
       <span class="octicon octicon-link"></span>
     </a>
-    The Structure of an Exploration
+    The Structure Of An Exploration
   </h2>
 
   <p>
@@ -91,7 +91,7 @@ <h2>
   </ul>
 
   <p>
-    Note that subsequent cards will also say something, and expect an answer
+    Note: That subsequent cards will also say something, and expect an answer
     from the learner. This is similar to a teacher asking a question of a
     student, and waiting for the answer.
   </p>

pages/TheExplorationEditor.html

@@ -58,7 +58,7 @@ <h4>
   <p>
     Here, you can write whatever you want the learner to read. The content can
     be about any topic/subject, and would end with a question or statement that
-    invites the learner to interact with Oppia. You can also include rich-text
+    invites the learner to interact with "Oppia". You can also include rich-text
     elements like images, videos and links.
   </p>
 

pages/WhatIsOppia.html

@@ -20,7 +20,7 @@ <h3>
   </h3>
   <p>
     Our mission is to make it possible for anyone to learn anything they want
-    to in an effective and enjoyable way.
+    to do in an effective and enjoyable way.
   </p>
   <p>
     One of the best ways to learn is by doing stuff and getting feedback. You