Small doc fixes and many tiny edits. (#439)

docs/courses/csintro/algorithms/activity.md

@@ -171,6 +171,7 @@ To comment a block of code:
 Notes
 * When you right-click on the icon that appears before the words on a block, notice that there are other options available to you that allow you to duplicate and delete blocks, as well as get help. Feel free to explore and use these as you code.
 * In JavaScript, you can add a comment by using two forward slashes, then typing your comment. The two forward slashes tell JavaScript that the following text (on that same line) is a comment.
+
 ```typescript
 // Display a happy face when button A is pressed.
 ```

docs/courses/csintro/algorithms/project.md

@@ -33,13 +33,39 @@ Sample fidget cube designs
 
 ## Assessment
 
-| | 4 | 3 | 2 | 1 |
-| - | - | - | - |
-| ============= | =============== | =============== | ============== | ============= |
-| Inputs | At least 4<br/>different inputs<br/>are successfully<br/>implemented | At least 3<br/>different inputs<br/> are successfully<br/>implemented | At least 2<br/>different inputs<br/>are successfully<br/>implemented | Fewer than 2<br/>different inputs<br/>are successfully<br/>implemented |
-| ============= | =============== | =============== | ============== | ============= |
-| Outputs | At least 4<br/>different outputs<br/>are successfully<br/>implemented | At least 3<br/>different outputs<br/>are successfully<br/>implemented | At least 2<br/>different outputs<br/>are successfully<br/>implemented | Fewer than 2<br/>different outputs<br/>are successfully<br/>implemented |
-| ============= | =============== | =============== | ============== | ============= |
-| Micro:bit<br/>program |Micro:bit<br/>program:<br/>- uses event<br/>handlers in a<br/>way that is<br/>integral to the<br/>program<br/>- compiles and<br/>runs as<br/>intended<br/>- includes<br/>meaningful<br/>comments | Micro:bit<br/>program lacks 1<br/>of the required<br/>elements | Micro:bit<br/>program lacks 2<br/>of the required<br/>elements | Micro:bit<br/>program lacks all<br/>or of the<br/>required<br/>elements |
-| ============= | =============== | =============== | ============== | ============= |
-| Collaboration<br/>reflection | Reflection piece<br/>includes:<br/>- brainstorming<br/>ideas<br/>- construction<br/>programming<br/>beta testing | Reflection piece<br/>lacks 1 of the<br/>required<br/>elements |	Reflection piece<br/>lacks 2 of the<br/>required<br/>elements | Reflection piece<br/>lacks 3 of the<br/>required<br/>elements |
+**Competency scores**: 4, 3, 2, 1
+
+### Inputs
+
+**4 =** At least 4 different inputs are successfully implemented.<br/>
+**3 =** At least 3 different inputs are successfully implemented.<br/>
+**2 =** At least 2 different inputs are successfully implemented.<br/>
+**1 =** Fewer than 2 different inputs are successfully implemented.
+
+### Outputs
+
+**4 =** At least 4 different outputs are successfully implemented.<br/>
+**3 =** At least 3 different outputs are successfully implemented.<br/>
+**2 =** At least 2 different outputs are successfully implemented.<br/>
+**1 =** Fewer than 2 different outputs are successfully implemented.
+
+### micro:bit program
+
+**4 =** micro:bit program:
+`*` uses event handlers in a way that is integral to the program<br/>
+`*` compiles and runs as intended<br/>
+`*` includes meaningful comments<br/>
+**3 =** micro:bit program lacks 1 of the required elements<br/>
+**2 =** micro:bit program lacks 2 of the required elements<br/>
+**1 =** micro:bit program lacks all of the required elements.
+
+### Collaboration reflection
+
+**4 =** Reflection piece includes:<br/>
+`*` brainstorming ideas<br/>
+`*` construction<br/>
+`*` programming<br/>
+`*` beta testing<br/>
+**3 =** Reflection piece lacks 1 of the required elements.<br/>
+**2 =** Reflection piece lacks 2 of the required elements.<br/>
+**1 =** Reflection piece lacks 3 of the required elements.

docs/courses/csintro/algorithms/unplugged.md

@@ -46,7 +46,7 @@ They can use pencil and paper or index cards.
 On paper, they can keep track of inputs and outputs in a table (see example above).
 With index cards, Player A can write each input on one side of an index card, hand the card to Player B, who then writes the corresponding output on the other side of the card.
 
-To begin:
+### To begin:
 * Player B decides on a mathematical function or bit of processing* that will be done on whatever input she receives from Player A. 
 * Player B should write down the function or bit of processing and set it aside, out of sight of Player A.
 * Player A then gives Player B a number to process.
@@ -57,7 +57,7 @@ To begin:
 * The goal is for Player A to figure out what function or bit of processing Player B is using in the fewest number of rounds of input/output possible.
 * After each student has had at least one chance to be the function machine, play more rounds as time permits.
 
-Notes: 
+### Notes: 
 * The difficulty level of the possible functions should be determined by the teacher and shared with the students ahead of playing. Alternately, the teacher can provide function cards that are handed out at random to be used by the players, rather than the players creating their own.
 * The player providing the input should not just guess what the function is. She should be able to explain why she thinks her input resulted in the given output.
 * Examples of ‘easier’ functions: 
@@ -73,18 +73,18 @@ Notes:
 ## Unplugged: Crazy Conditionals
 This is a fun, interactive exercise to introduce conditionals and event handlers as computer processing.  Read through the entire activity and adjust as needed for your class and classroom.
  
-Preparation: 
+### Preparation: 
 * Print & cut into strips with one conditional on each strip
 * Note that some of the same conditionals can be given to multiple students, while other conditionals are to be given to just one student.
 * Except for the first ‘BEGIN’ conditional, hand out the conditionals PRINT SIDE DOWN. 
 * Besides the ‘BEGIN’ and ‘STOP’ conditional, give at least two other conditionals to each student. A lesson from this is that it is challenging for a student to keep track of a lot of different conditionals, though not so for a computer! : )
  
-Notes: 
+### Notes: 
 * Some of the same conditionals can be given to multiple students, while other conditionals are to be given to just one student.
 * Technically these conditionals are all event handlers because the students are simply waiting for a specific event to trigger them into action.
 * Unless instructed otherwise, students do not speak or make noise during this activity.
 
-Extensions/Variations: 
+### Extensions/Variations: 
 * Add AND, OR, AND/OR statements to the conditionals.
 * Create nested IF’s
 * Let students create the IF’s