freeCodeCamp · camperbot · Dec 4, 2024 · Dec 4, 2024
diff --git a/...eb-design-22/learn-html-by-building-a-cat-photo-app/5ef9b03c81a63668521804dc.md b/...eb-design-22/learn-html-by-building-a-cat-photo-app/5ef9b03c81a63668521804dc.md
@@ -9,15 +9,15 @@ dashedName: step-46
 
 對於需要從多個選項中獲得一個答案的問題，你可以使用單選按鈕。
 
-這是一個選項爲 `cat` 的單選按鈕示例：
+Here is an example of a radio button with the text set as `cat`:
 
 ```html
 <input type="radio"> cat
 ```
 
 請記住，`input` 元素是一個空元素。
 
-在文本輸入之前，添加一個具有如下選項的單選按鈕：
+Before the text input, add a radio button with the text set as:
 
 `Indoor`
 

diff --git a/...eb-design-22/learn-html-by-building-a-cat-photo-app/5ef9b03c81a63668521804e2.md b/...eb-design-22/learn-html-by-building-a-cat-photo-app/5ef9b03c81a63668521804e2.md
@@ -9,7 +9,7 @@ dashedName: step-56
 
 對於可能有多個答案的問題，表單通常使用複選框。 `input` 元素，`type` 屬性值設置爲 `checkbox`，就創建一個複選框。
 
-在你剛剛添加的 `legend` 元素下，添加一個 `input`，將其 `type` 屬性設置爲 `checkbox`，併爲其指定選項：
+Under the `legend` element you just added, add an `input` with its `type` attribute set to `checkbox` and its text set to:
 
 `Loving`
 

diff --git a/...oductory-javascript-by-building-a-pyramid-generator/660f383d4c772c12ff59904b.md b/...oductory-javascript-by-building-a-pyramid-generator/660f383d4c772c12ff59904b.md
@@ -7,7 +7,7 @@ dashedName: step-70
 
 # --description--
 
-你可以將完整的表達式作爲參數傳遞。 該函數將接收該表達式的求值結果。 例如，這兩個函數調用將產生相同的結果：
+你可以將完整的表達式作爲參數傳遞。 該函數將接收該表達式的求值結果。 For example, these two function calls below would yield the same result. (Note that the order of operations rule PEMDAS—Parenthesis, Exponents, Multiplication, Division, Addition, Subtraction—applies):
 
 ```js
 test(2 * 3 + 1);

diff --git a/...opers/learn-conversation-starters-in-the-break-room/657dc71c76da6e475ad4eb4f.md b/...opers/learn-conversation-starters-in-the-break-room/657dc71c76da6e475ad4eb4f.md
@@ -10,7 +10,7 @@ Sophie: Sometimes, but we normally discuss tasks we plan on tackling for the wee
 
 # --description--
 
-`to tackle tasks` refers to trying to finish tasks as best as possible.
+`To tackle tasks` refers to trying to finish tasks as best as possible.
 
 For example, programmers usually have to tackle coding tasks.
 

diff --git a/...-developers/learn-how-to-talk-about-past-activities/66609e8c75137f49fd9c25fd.md b/...-developers/learn-how-to-talk-about-past-activities/66609e8c75137f49fd9c25fd.md
@@ -1,8 +1,8 @@
 ---
 id: 66609e8c75137f49fd9c25fd
-title: "Dialogue 1: I'm Tom"
+title: "Dialogue 1: The Latest User Feedback"
 challengeType: 21
-dashedName: dialogue-1-im-tom
+dashedName: dialogue-1-the-latest-user-feedback
 ---
 
 # --description--
@@ -15,44 +15,159 @@ dashedName: dialogue-1-im-tom
 
 # --scene--
 
+
 ```json
 {
-  "setup": {
-    "background": "chaos.png",
-    "characters": [
-      {
-        "character": "David",
-        "position": {"x":50,"y":80,"z":8},
-        "opacity": 0
-      }
-    ],
-    "audio": {
-      "filename": "1.1-1.mp3",
-      "startTime": 1,
-      "startTimestamp": 5.7,
-      "finishTimestamp": 6.48
-    }
-  },
-  "commands": [
-    {
-      "character": "David",
-      "opacity": 1,
-      "startTime": 0
-    },
-    {
-      "character": "David",
-      "startTime": 1,
-      "finishTime": 0.78,
-      "dialogue": {
-        "text": "I'm Tom.",
-        "align": "center"
-      }
-    },
-    {
-      "character": "Tom",
-      "opacity": 0,
-      "startTime": 1.28
-    }
-  ]
+ "setup": {
+   "background": "interview-room3.png",
+   "characters": [
+     {
+       "character": "James",
+       "position": { "x": -25, "y": 0, "z": 1 }
+     },
+     {
+       "character": "Linda",
+       "position": { "x": 125, "y": 0, "z": 1 }
+     }
+   ],
+   "audio": {
+     "filename": "B1_3-1.mp3",
+     "startTime": 1
+   },
+   "alwaysShowDialogue": true
+ },
+ "commands": [
+   {
+     "character": "James",
+     "position": { "x": 25, "y": 0, "z": 1 },
+     "startTime": 0
+   },
+   {
+     "character": "Linda",
+     "position": { "x": 70, "y": 0, "z": 1 },
+     "startTime": 0.5
+   },
+   {
+     "character": "James",
+     "startTime": 1,
+     "finishTime": 3.56,
+     "dialogue": {
+       "text": "Have you seen the latest user feedback?",
+       "align": "left"
+     }
+   },
+   {
+     "character": "James",
+     "startTime": 3.56,
+     "finishTime": 8.86,
+     "dialogue": {
+       "text": "They've mentioned some elements of our homepage aren't displaying correctly on mobile devices.",
+       "align": "left"
+     }
+   },
+   {
+     "character": "Linda",
+     "startTime": 9.88,
+     "finishTime": 15.06,
+     "dialogue": {
+       "text": "Yes, I've reviewed the reports. It seems we've got a UI display issue across different screen sizes.",
+       "align": "right"
+     }
+   },
+   {
+     "character": "James",
+     "startTime": 15.4,
+     "finishTime": 17.5,
+     "dialogue": {
+       "text": "Have we fixed anything like this before?",
+       "align": "left"
+     }
+   },
+   {
+     "character": "Linda",
+     "startTime": 18.02,
+     "finishTime": 21.16,
+     "dialogue": {
+       "text": "No, we haven't, but we've solved similar issues on other projects.",
+       "align": "right"
+     }
+   },
+   {
+     "character": "James",
+     "startTime": 21.9,
+     "finishTime": 25.24,
+     "dialogue": {
+       "text": "Have you had the time to identify which elements are causing the trouble?",
+       "align": "left"
+     }
+   },
+   {
+     "character": "Linda",
+     "startTime": 25.24,
+     "finishTime": 30.5,
+     "dialogue": {
+       "text": "Yes, I have. The navigation bar and the footer haven't been adapting well to smaller screens.",
+       "align": "right"
+     }
+   },
+   {
+     "character": "James",
+     "startTime": 31.3,
+     "finishTime": 34.86,
+     "dialogue": {
+       "text": "Have we received any detailed reports from users about this issue?",
+       "align": "left"
+     }
+   },
+   {
+     "character": "Linda",
+     "startTime": 35.5,
+     "finishTime": 40.9,
+     "dialogue": {
+       "text": "Yes, a few actually. They've emailed us screenshots showing how elements overlap on their devices.",
+       "align": "right"
+     }
+   },
+   {
+     "character": "James",
+     "startTime": 41.78,
+     "finishTime": 46.06,
+     "dialogue": {
+       "text": "Alright, what's our next step? Has the development team been informed about this?",
+       "align": "left"
+     }
+   },
+   {
+     "character": "Linda",
+     "startTime": 46.36,
+     "finishTime": 49.1,
+     "dialogue": {
+       "text": "Not yet, but I've scheduled a meeting for tomorrow morning.",
+       "align": "right"
+     }
+   },
+   {
+     "character": "Linda",
+     "startTime": 49.4,
+     "finishTime": 52.4,
+     "dialogue": {
+       "text": "We'll go over the proposed fixes and decide on the best approach.",
+       "align": "right"
+     }
+   },
+   {
+     "character": "Linda",
+     "position": { "x": 125, "y": 0, "z": 1 },
+     "startTime": 52.9
+   },
+   {
+     "character": "James",
+     "position": { "x": -25, "y": 0, "z": 1 },
+     "startTime": 53.4
+   }
+ ]
 }
 ```
+
+
+
diff --git a/...-developers/learn-how-to-talk-about-past-activities/66c8e6cdd7a69d2878880fbf.md b/...-developers/learn-how-to-talk-about-past-activities/66c8e6cdd7a69d2878880fbf.md
@@ -0,0 +1,88 @@
+---
+id: 66c8e6cdd7a69d2878880fbf
+title: Task 1
+challengeType: 22
+dashedName: task-1
+---
+
+<!-- (Audio)James: Have you seen the latest user feedback?  -->
+
+# --instructions--
+
+Listen to the audio and complete the sentence below.
+
+# --fillInTheBlank--
+
+## --sentence--
+
+`Have you BLANK the latest user feedback?`
+
+## --blanks--
+
+`seen`
+
+### --feedback--
+
+The past participle of `see` is irregular, and it is not `see` or `saw`.
+
+# --explanation--
+
+The `Present Perfect` tense is used to talk about actions or experiences that happened at some point before now.
+
+Use this structure to talk about something that happened before now, but **where the exact time isn't important**.
+
+To form the `Present Perfect` tense, use `have` or `has` followed by the past participle of the verb.
+
+The past participle of the verb `see` is `seen`. It's irregular, which means it doesn't just add `-ed` like regular verbs. For example:
+
+- `I have seen the report.` - At some point before now, you saw the report.
+
+- `She has seen the report.` - At some point before now, she saw the report.
+
+# --scene--
+
+```json
+{
+  "setup": {
+    "background": "interview-room3.png",
+    "characters": [
+      {
+        "character": "James",
+        "position": {
+          "x": 50,
+          "y": 15,
+          "z": 1.2
+        },
+        "opacity": 0
+      }
+    ],
+    "audio": {
+      "filename": "B1_3-1.mp3",
+      "startTime": 1,
+      "startTimestamp": 0,
+      "finishTimestamp": 2.76
+    }
+  },
+  "commands": [
+    {
+      "character": "James",
+      "opacity": 1,
+      "startTime": 0
+    },
+    {
+      "character": "James",
+      "startTime": 1,
+      "finishTime": 3.76,
+      "dialogue": {
+        "text": "Have you seen the latest user feedback?",
+        "align": "center"
+      }
+    },
+    {
+      "character": "James",
+      "opacity": 0,
+      "startTime": 4.26
+    }
+  ]
+}
+```