Tweak iP PR allocation table

admin/admin-tasks-fragment.md

@@ -143,7 +143,7 @@ The info in the following panels differs from TIC4001.
 
 {{ embed_topic("peerEvaluations.md#intro", "Admin " + icon_embedding + " Peer Evaluations → Introduction", "3", indent="2") }}
 {{ embed_topic("peerEvaluations.md#practicePeerEvaluations", "Admin " + icon_embedding + " Peer Evaluations → Session: Practice Peer Evaluation", "1", indent="2", status="expanded") }}
-{{ embed_topic("appendixB-policies.md#policy-deadlineExtensions", "Admin " + icon_embedding + " **Module Policies → Policy on Deadline Extensions**", "3", indent="2", type="primary") }}
+{{ embed_topic("appendixB-policies.md#policy-deadlineExtensions", "Admin " + icon_embedding + " **Module Policies → Policy on Deadline Extensions**", "4", indent="2") }}
 </div>
 {#====================================================================================================================#}
 <span id="heading_submit_midterm_feedback_for_the_module">[optional] Submit mid-term feedback for the module</span>

admin/common-tutorials-fragment.md

@@ -55,11 +55,11 @@
 
 {% macro get_pr_link(username) -%}[{{ username }}]({{ url_module_org }}/{{ ip_repo_name }}/pulls/{{ username }}){%- endmacro %}
 <div id="show-ip-peer-review-allocation-1">
-<panel header="**iP PR review allocation** (click to expand)" minimized >
+<panel header="**Review allocation for the ==first== PR review** (click to expand)" minimized >
 {% from "_module-" + module + "/studentData-fragment.md" import ip_pr_review_allocation with context %}
 Tutorial | Reviewer | First PR to review | Backup PR to review
 ---------|----------|--------------------|---------------------{% for line in ip_pr_review_allocation  %}
-{{ line[0] }} | {{ line[1] }} | {{ get_pr_link(line[2]) }} | {{ get_pr_link(line[3]) }}{% endfor %}
+{{ line[0] }} | {{ line[1] }} | {{ get_pr_link(line[2]) }} | <small>%%backup:%% {{ get_pr_link(line[3]) }}</small>{% endfor %}
 {% if not ip_pr_review_allocation | length %}Allocation not available yet... {% endif %}
 </panel>
 <p/>
@@ -86,11 +86,11 @@ Alternatively, you can use PR labels (if any) to filter PRs/Issues.<br>
 
 </div>
 <div id="show-ip-peer-review-allocation-2">
-<panel header="**iP PR review allocation** (click to expand)" minimized >
+<panel header="**Review allocation for the ==second== PR review** (click to expand)" minimized >
 {% from "_module-" + module + "/studentData-fragment.md" import ip_pr_review_allocation with context %}
 Tutorial | Reviewer | Second PR to review | Backup PR to review
 ---------|----------|---------------------|---------------------{% for line in ip_pr_review_allocation  %}
-{{ line[0] }} | {{ line[1] }} | {{ get_pr_link(line[4]) }} | {{ get_pr_link(line[5]) }}{% endfor %}
+{{ line[0] }} | {{ line[1] }} | {{ get_pr_link(line[4]) }} | <small>%%backup:%% {{ get_pr_link(line[5]) }}</small>{% endfor %}
 {% if not ip_pr_review_allocation | length %}Allocation not available yet... {% endif %}
 </panel>
 <p/>

admin/tp-tasks-fragment.md

@@ -298,9 +298,9 @@ As we are still at the early stages of identifying a problem to solve, do not th
 
 * **What format?**: You may use a sentence format or a table format but do maintain the prescribed three-part structure of a user story. In particular, ==try to include the _benefit_ part in most user stories== as that will come in handy when prioritizing user stories later.
 
-* **How to record?**<br>
-  ==Keep records of intermediate steps (e.g., persona, scenarios)== in your collaborative project document started in the previous week.<br>
-  You can ~~write each user story in a piece of paper (e.g. yellow sticky note, index card, or just pieces of paper about the size of a playing card). Alternatively you can~~ use an online tool (some examples given in <trigger trigger="click" for="modal:v10-onlinetools">[Textbook {{ icon_embedding }} Specifying Requirements → UserStories → Usage → (panel) Tool Examples ]</trigger>).
+* **Submission** (to be checked by the tutor later):<br>
+  * Intermediate steps (e.g., persona, scenarios): Keep records these in your collaborative project document started in the previous week.
+  * Brainstormed user stories:  Record them using an <!--~~write each user story in a piece of paper (e.g. yellow sticky note, index card, or just pieces of paper about the size of a playing card). Alternatively you can~~--> online tool (some examples given in <trigger trigger="click" for="modal:v10-onlinetools">[Textbook {{ icon_embedding }} Specifying Requirements → UserStories → Usage → (panel) Tool Examples ]</trigger>).
 
 <modal large header="Textbook {{ icon_embedding }}" id="modal:v10-brainstorming">
 <include src="../book/gatheringRequirements/brainstorming/unit-inElsewhere-asFlat.md" boilerplate/>
@@ -315,7 +315,7 @@ As we are still at the early stages of identifying a problem to solve, do not th
 </modal>
 
 
-<div tags="m--cs2103 m--tic4002" class="indented-level2">
+<div tags="m--cs2103 m--tic4001 m--tic4002" class="indented-level2">
 
 {{ icon_tip }} **If you choose to use the GitHub issue tracker to manage user stories**, you need to set up your team's GitHub organization, team repo, and its issue tracker first. Instructions for doing those steps are in the panel below.
 

schedule/week3/admin-tic2002-fragment.md

@@ -39,7 +39,8 @@
 
 #### {{ thumb(1) }} Setup Duke project on your computer {{ timing_badge("during/after the lecture", "secondary") }}
 
-1. **Fork** [{{ url_module_org }}/duke]({{ url_module_org }}/duke). The relevant textbook topic is given below for our reference.
+1. **Fork** [{{ url_module_org }}/duke]({{ url_module_org }}/duke). The relevant textbook topic is given below for your reference.<br>
+   {{ icon_important_big_red }} Please ==retain the repon name `duke`== when forking. If you name your fork as something else, our grading scripts will not be able to find your fork.
 
    {{ embed_topic("../../book/gitAndGithub/fork/text.md#body", "Textbook " + icon_embedding + " Git & GitHub → **Forking**", "1", indent=2) }}