mirror of
https://github.com/freeCodeCamp/freeCodeCamp.git
synced 2026-03-06 06:39:18 -05:00
feat(curriculum): add English curriculum block 8.1 sharing progress and accomplishments (#54319)
Co-authored-by: Naomi <nhcarrigan@gmail.com> Co-authored-by: Tom <20648924+moT01@users.noreply.github.com> Co-authored-by: Nielda Karla <90112119+nieldakarla@users.noreply.github.com>
This commit is contained in:
@@ -9,8 +9,176 @@
|
||||
"superBlock": "a2-english-for-developers",
|
||||
"challengeOrder": [
|
||||
{
|
||||
"id": "655cd38e0ee8668d87f50f82",
|
||||
"title": "Dialogue: Placeholder"
|
||||
"id": "66100326d773b61282509e50",
|
||||
"title": "Dialogue 1: During a Weekly Meeting"
|
||||
},
|
||||
{
|
||||
"id": "661003c35e5ba713abd2da6c",
|
||||
"title": "Task 1"
|
||||
},
|
||||
{
|
||||
"id": "6610041a61d5ec13feffff07",
|
||||
"title": "Task 2"
|
||||
},
|
||||
{
|
||||
"id": "6610056e633ce41466b6c5bc",
|
||||
"title": "Task 3"
|
||||
},
|
||||
{
|
||||
"id": "661005bbe1801e14c303a57a",
|
||||
"title": "Task 4"
|
||||
},
|
||||
{
|
||||
"id": "66100646290700150caff732",
|
||||
"title": "Task 5"
|
||||
},
|
||||
{
|
||||
"id": "661215c06938a71ad4101c93",
|
||||
"title": "Task 6"
|
||||
},
|
||||
{
|
||||
"id": "661216bbf6d9a51b409172a8",
|
||||
"title": "Task 7"
|
||||
},
|
||||
{
|
||||
"id": "661216ff45b1871b85f57a1a",
|
||||
"title": "Task 8"
|
||||
},
|
||||
{
|
||||
"id": "6612181d89fdfc1c2f44309d",
|
||||
"title": "Task 9"
|
||||
},
|
||||
{
|
||||
"id": "661218bc905fb61c898221b4",
|
||||
"title": "Task 10"
|
||||
},
|
||||
{
|
||||
"id": "66121954a1cde81cd252ef26",
|
||||
"title": "Task 11"
|
||||
},
|
||||
{
|
||||
"id": "66121a02da620e1d25ff63d4",
|
||||
"title": "Task 12"
|
||||
},
|
||||
{
|
||||
"id": "66121b3a462fe01da4816b39",
|
||||
"title": "Task 13"
|
||||
},
|
||||
{
|
||||
"id": "66122a393fd32d2a4876ca95",
|
||||
"title": "Dialogue 2: A Manager and a Direct Report in a Performance Review"
|
||||
},
|
||||
{
|
||||
"id": "66122a6093ba082abb2cd136",
|
||||
"title": "Task 14"
|
||||
},
|
||||
{
|
||||
"id": "66122ab30afc8e2b1f42b78a",
|
||||
"title": "Task 15"
|
||||
},
|
||||
{
|
||||
"id": "66122b7d6f1f182bb1fe0338",
|
||||
"title": "Task 16"
|
||||
},
|
||||
{
|
||||
"id": "661253cc9fb5ee2d01a0d6a8",
|
||||
"title": "Task 17"
|
||||
},
|
||||
{
|
||||
"id": "661254cf9474ed2da90fec1b",
|
||||
"title": "Task 18"
|
||||
},
|
||||
{
|
||||
"id": "66125530a1a9e92e0e08d594",
|
||||
"title": "Task 19"
|
||||
},
|
||||
{
|
||||
"id": "661255c3b6ea612e984a62b8",
|
||||
"title": "Task 20"
|
||||
},
|
||||
{
|
||||
"id": "66125666f8437c2f3616045e",
|
||||
"title": "Task 21"
|
||||
},
|
||||
{
|
||||
"id": "661256fe823f142fb9858beb",
|
||||
"title": "Task 22"
|
||||
},
|
||||
{
|
||||
"id": "66126744e24b0a31255718a7",
|
||||
"title": "Task 23"
|
||||
},
|
||||
{
|
||||
"id": "661267c5ac355931ab1f933d",
|
||||
"title": "Task 24"
|
||||
},
|
||||
{
|
||||
"id": "6612693507cbd43269ae64e0",
|
||||
"title": "Task 25"
|
||||
},
|
||||
{
|
||||
"id": "661269c4ccdd4132db7517b8",
|
||||
"title": "Task 26"
|
||||
},
|
||||
{
|
||||
"id": "66126a21821998335a86a34b",
|
||||
"title": "Task 27"
|
||||
},
|
||||
{
|
||||
"id": "66127192c932be37ed0217e7",
|
||||
"title": "Dialogue 3: Sharing Accomplishments over Lunch"
|
||||
},
|
||||
{
|
||||
"id": "661271c2b16aff3870604148",
|
||||
"title": "Task 28"
|
||||
},
|
||||
{
|
||||
"id": "6612727ec0a11b390b8e92cb",
|
||||
"title": "Task 29"
|
||||
},
|
||||
{
|
||||
"id": "6612752978bcc239ae7b60da",
|
||||
"title": "Task 30"
|
||||
},
|
||||
{
|
||||
"id": "6612757ffdc16b3a22b08427",
|
||||
"title": "Task 31"
|
||||
},
|
||||
{
|
||||
"id": "6612762a058bb43b960e91ca",
|
||||
"title": "Task 32"
|
||||
},
|
||||
{
|
||||
"id": "66127678c88f183c0312d8e8",
|
||||
"title": "Task 33"
|
||||
},
|
||||
{
|
||||
"id": "66127755a52efa3c9a73065b",
|
||||
"title": "Task 34"
|
||||
},
|
||||
{
|
||||
"id": "661277970c67233d02f138de",
|
||||
"title": "Task 35"
|
||||
},
|
||||
{
|
||||
"id": "661278160653ee3d9040ed68",
|
||||
"title": "Task 36"
|
||||
},
|
||||
{
|
||||
"id": "66127850c4415c3df1b4e99a",
|
||||
"title": "Task 37"
|
||||
},
|
||||
{
|
||||
"id": "6612792bc77de13e8f2af3ad",
|
||||
"title": "Task 38"
|
||||
},
|
||||
{
|
||||
"id": "6612797faf03663ef83f4459",
|
||||
"title": "Task 39"
|
||||
},
|
||||
{
|
||||
"id": "661279c8d3bf0f3f6f23f21f",
|
||||
"title": "Task 40"
|
||||
}
|
||||
],
|
||||
"helpCategory": "English"
|
||||
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
id: 66100326d773b61282509e50
|
||||
title: "Dialogue 1: During a Weekly Meeting"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-1-during-a-weekly-meeting
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video below to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
id: 661003c35e5ba713abd2da6c
|
||||
title: Task 1
|
||||
challengeType: 22
|
||||
dashedName: task-1
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: Hi everyone, let's start our weekly project update meeting. Sarah, would you like to begin?
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`Daily` means something happens every day. For example, `I check my email daily.`
|
||||
|
||||
`Weekly` means something happens once a week. Like a meeting that happens every Monday.
|
||||
|
||||
`Monthly` means something happens once a month. For instance, `We have a team lunch monthly.`
|
||||
|
||||
`Yearly` means something happens once a year. An example is, `Our company hosts a big event yearly.`
|
||||
|
||||
Understanding these time intervals is important in both everyday life and in professional settings, like in project meetings or planning.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Hi everyone, let's start our _ project update meeting. Sarah, would you like to _?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`weekly`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to something happening once a week. In this case, the project update meeting occurs every week.
|
||||
|
||||
---
|
||||
|
||||
`begin`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means to start something. Bob is asking Sarah if she would like to start talking about her part of the project.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
id: 6610041a61d5ec13feffff07
|
||||
title: Task 2
|
||||
challengeType: 22
|
||||
dashedName: task-2
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Sure. This week, I worked on the user interface design. I designed a new layout for the app, and I created some mockups to show how it will look.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
An `interface` in technology, especially in apps or websites, is the part that people interact with. It's like the front of a TV that has buttons and a screen.
|
||||
|
||||
A `mockup` is a model or a draft of something. In design, it's like drawing a sketch of a room before you decorate it to see how it might look.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Sure. This week, I worked on the user _ design. I designed a new layout for the app, and I created some _ to show _ it will look.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`interface`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it refers to the part of the app that users will see and interact with.
|
||||
|
||||
---
|
||||
|
||||
`mockups`
|
||||
|
||||
### --feedback--
|
||||
|
||||
They are preliminary models or drafts used to give an early idea of what the final product will look like.
|
||||
|
||||
---
|
||||
|
||||
`how`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used to introduce a way or manner, in this case, explaining the app's design.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 6610056e633ce41466b6c5bc
|
||||
title: Task 3
|
||||
challengeType: 19
|
||||
dashedName: task-3
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Sure. This week, I worked on the user interface design. I designed a new layout for the app, and I created some mockups to show how it will look.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What did Sarah work on this week?
|
||||
|
||||
## --answers--
|
||||
|
||||
She fixed bugs in the app's code.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. Sarah's work was focused on design aspects, not on fixing coding bugs.
|
||||
|
||||
---
|
||||
|
||||
She worked on the user interface design, creating a new layout and mockups.
|
||||
|
||||
---
|
||||
|
||||
She conducted user testing for the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While user testing is important, it was not mentioned as part of Sarah's tasks for this week.
|
||||
|
||||
---
|
||||
|
||||
She wrote documentation for the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah's focus was on design elements, not on writing documentation.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,55 @@
|
||||
---
|
||||
id: 661005bbe1801e14c303a57a
|
||||
title: Task 4
|
||||
challengeType: 22
|
||||
dashedName: task-4
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: That's great, Sarah! I’ve also been pretty busy this week. I tested the new feature we added last week. It seems to be working well. And I found a few minor issues that we need to fix.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`Pretty` is used to make an adjective stronger. For example, `I'm pretty tired` means I'm quite tired.
|
||||
|
||||
`Minor` means small or not very important. For example, `There are a few minor problems with my bike` means there are some small problems.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`That's great, Sarah! I’ve also been _ busy this week. I tested the new _ we added last week. It _ to be working well. And I found a few _ issues that we need to fix.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`pretty`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used here as an intensifier to describe the level of busyness, meaning Bob was quite busy.
|
||||
|
||||
---
|
||||
|
||||
`feature`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to a specific function or part of a product, in this case, something new added to their project.
|
||||
|
||||
---
|
||||
|
||||
`seems`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This word is used to express an appearance or impression, here indicating that the new feature appears to work well.
|
||||
|
||||
---
|
||||
|
||||
`minor`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It indicates that the issues found were not very large or critical.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 66100646290700150caff732
|
||||
title: Task 5
|
||||
challengeType: 19
|
||||
dashedName: task-5
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: That's great, Sarah! I’ve also been pretty busy this week. I tested the new feature we added last week. It seems to be working well. And I found a few minor issues that we need to fix.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What did Bob do this week?
|
||||
|
||||
## --answers--
|
||||
|
||||
He tested the new feature and found a few minor issues.
|
||||
|
||||
---
|
||||
|
||||
He was on vacation.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect as Bob mentions he was busy testing a new feature and finding issues.
|
||||
|
||||
---
|
||||
|
||||
He worked on creating a new app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While Bob was busy with a feature, there's no mention of him creating a new app.
|
||||
|
||||
---
|
||||
|
||||
He attended a technology conference.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob's activities were related to testing and issue-finding, not attending a conference.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
id: 661215c06938a71ad4101c93
|
||||
title: Task 6
|
||||
challengeType: 22
|
||||
dashedName: task-6
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Thanks for catching those. As for me, I also finished the market research report. I presented it to the team yesterday. We’ve gathered valuable data that will help us make informed decisions.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`To catch` can have the meaning of noticing or finding something, often a problem or mistake. Like when you say, `I caught a spelling error in the report.` Here, `caught` is the past tense of `catch`.
|
||||
|
||||
A `market` is a place or area where goods are sold, or in business, it refers to the group of people who might buy a product. For example, `We studied the smartphone market.`
|
||||
|
||||
`To gather` means to collect or bring together. In business, you might `gather` information or data, like `We gathered customer feedback.`
|
||||
|
||||
An `informed decision` is a choice made based on good information or knowledge. For example, `After researching, we made an informed decision about our project.`
|
||||
|
||||
These terms are useful in business and technology for discussing work and decision-making.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Thanks for _ those. As for me, I also finished the _ research report. I presented it to the team yesterday. We’ve _ valuable data that will help us make _ decisions.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`catching`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it refers to identifying or noticing something, like issues or errors.
|
||||
|
||||
---
|
||||
|
||||
`market`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to the area of study or interest in business, like studying consumer trends or needs.
|
||||
|
||||
---
|
||||
|
||||
`gathered`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means collected. Here, it refers to collecting data or information.
|
||||
|
||||
---
|
||||
|
||||
`informed`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means the decisions are based on good information or knowledge.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661216bbf6d9a51b409172a8
|
||||
title: Task 7
|
||||
challengeType: 19
|
||||
dashedName: task-7
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Thanks for catching those. As for me, I also finished the market research report. I presented it to the team yesterday. We’ve gathered valuable data that will help us make informed decisions.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What does `gathered` mean in Sarah's statement about the market research report?
|
||||
|
||||
## --answers--
|
||||
|
||||
She organized a meeting to discuss the report.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. `Gathered` in this context refers to collecting data, not organizing meetings.
|
||||
|
||||
---
|
||||
|
||||
She collected valuable data from the research.
|
||||
|
||||
---
|
||||
|
||||
She wrote the main conclusions of the report.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While summarizing is important, `gathered` here specifically refers to the collection of data, not writing conclusions.
|
||||
|
||||
---
|
||||
|
||||
She designed the layout of the report.
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Gathered` doesn't relate to designing; it's about collecting information or data.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,38 @@
|
||||
---
|
||||
id: 661216ff45b1871b85f57a1a
|
||||
title: Task 8
|
||||
challengeType: 22
|
||||
dashedName: task-8
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: Excellent work, team! I organized a meeting with the client to discuss their feedback. They liked our progress so far and expressed satisfaction with our work.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`Satisfaction` is a feeling of happiness or pleasure when you achieve something or when something meets your expectations. In business, `customer satisfaction` is very important. It means the customers are happy with the products or services provided.
|
||||
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Excellent work, team! I _ a meeting with the client to discuss their feedback. They liked our progress so far and expressed _ with our work.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`organized`
|
||||
|
||||
### --feedback--
|
||||
|
||||
The word is used here to describe the action of planning or arranging a meeting.
|
||||
|
||||
---
|
||||
|
||||
`satisfaction`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it refers to the clients being pleased or content with the team's work.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 6612181d89fdfc1c2f44309d
|
||||
title: Task 9
|
||||
challengeType: 19
|
||||
dashedName: task-9
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: Excellent work, team! I organized a meeting with the client to discuss their feedback. They liked our progress so far and expressed satisfaction with our work.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
An `outcome` is the result or effect of an action, situation, or event. It's what happens as a result of something. In the context of technology, for example, the `outcome` of a software update might be improved performance or new features.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What is the `outcome` of the meeting Bob organized with the client?
|
||||
|
||||
## --answers--
|
||||
|
||||
The client requested major changes to the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. Bob mentioned that the client expressed satisfaction, not a request for major changes.
|
||||
|
||||
---
|
||||
|
||||
The client canceled the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Canceling the project contradicts the client's expressed satisfaction as mentioned by Bob.
|
||||
|
||||
---
|
||||
|
||||
The client was satisfied with the team's progress.
|
||||
|
||||
---
|
||||
|
||||
The team needs to start over with the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect as it contradicts the client's satisfaction with the current progress.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
id: 661218bc905fb61c898221b4
|
||||
title: Task 10
|
||||
challengeType: 22
|
||||
dashedName: task-10
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: That's wonderful to hear. It sounds like we have achieved a lot this week.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`Wonderful` means something is very good or pleasant. It's often used to express happiness or satisfaction, like when someone says, `The news is wonderful!`
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`That's _ to hear. It sounds like we have _ a lot this week.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`wonderful`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used here to express happiness or satisfaction about the news or information received.
|
||||
|
||||
---
|
||||
|
||||
`achieved`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to successfully completing or reaching a goal, in this case, the team's accomplishments for the week.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 66121954a1cde81cd252ef26
|
||||
title: Task 11
|
||||
challengeType: 19
|
||||
dashedName: task-11
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: That's wonderful to hear. It sounds like we have achieved a lot this week.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Remember, the present perfect tense, formed with `have` or `has` plus the past participle of a verb, is used to describe actions or states that occurred at an unspecified time before now. The focus is on the result of the action, not the specific time it occurred.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What does `have achieved` in Sarah's statement imply about the team's work?
|
||||
|
||||
## --answers--
|
||||
|
||||
The team has successfully reached goals or completed tasks recently.
|
||||
|
||||
---
|
||||
|
||||
The team will achieve their goals in the future.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect because `have achieved` refers to accomplishments already made, not future goals.
|
||||
|
||||
---
|
||||
|
||||
The team had goals but did not achieve them.
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Have achieved` indicates successful accomplishment, not failure to achieve goals.
|
||||
|
||||
---
|
||||
|
||||
The team is planning to start working soon.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The use of `have achieved` implies that the work has already been done, not just planned.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
id: 66121a02da620e1d25ff63d4
|
||||
title: Task 12
|
||||
challengeType: 22
|
||||
dashedName: task-12
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: Yes, it's been a productive week. Let's keep up the good work. Don't forget to report any issues and communicate with the team as needed. Our collaboration is key to our success.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`To be key to something` means to be very important or crucial. For example, in a team, `Good communication is key to success` means that success depends a lot on good communication.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Yes, it's _ a productive week. Let's keep _ the good work. Don't _ to report any issues and communicate with the team as _. Our collaboration is _ to our success.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`been`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It indicates a past experience or state, here referring to the week being productive.
|
||||
|
||||
---
|
||||
|
||||
`up`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It's part of a phrase meaning to continue in the same manner. Bob is encouraging the team to continue their good work.
|
||||
|
||||
---
|
||||
|
||||
`forget`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means to be unable to remember something or someone. Bob is emphasizing the importance of remembering to do something, like reporting issues.
|
||||
|
||||
---
|
||||
|
||||
`needed`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It suggests doing something when it is necessary, in this case, communicating with the team.
|
||||
|
||||
---
|
||||
|
||||
`key`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it means very important. Bob is emphasizing that collaboration is crucial to their success.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 66121b3a462fe01da4816b39
|
||||
title: Task 13
|
||||
challengeType: 19
|
||||
dashedName: task-13
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Bob: Yes, it's been a productive week. Let's keep up the good work. Don't forget to report any issues and communicate with the team as needed. Our collaboration is key to our success.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What instructions does Bob give to the team?
|
||||
|
||||
## --answers--
|
||||
|
||||
To take a break and relax for the next week
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. Bob emphasizes continuing the good work and communicating, not taking a break.
|
||||
|
||||
---
|
||||
|
||||
To stop reporting issues and work independently
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is contrary to Bob's instructions. He specifically asks to report any issues and communicate with the team.
|
||||
|
||||
---
|
||||
|
||||
To start working on a different project
|
||||
|
||||
### --feedback--
|
||||
|
||||
Bob's focus is on maintaining the current good work and teamwork, not on starting a new project.
|
||||
|
||||
---
|
||||
|
||||
To continue the good work, report any issues, and communicate as needed
|
||||
|
||||
## --video-solution--
|
||||
|
||||
4
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
id: 66122a393fd32d2a4876ca95
|
||||
title: "Dialogue 2: A Manager and a Direct Report in a Performance Review"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-2-a-manager-and-a-direct-report-in-a-performance-review
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video below to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
id: 66122a6093ba082abb2cd136
|
||||
title: Task 14
|
||||
challengeType: 22
|
||||
dashedName: task-14
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Maria: Hi there, Brian. It's time for our performance review. How's everything going?
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
A `performance review` is a regular evaluation of an employee's work by their manager. It's a time to discuss how well you are doing your job, any successes you've had, and areas where you can improve.
|
||||
|
||||
For example, in a tech company, a `performance review` might focus on the number of projects completed, the quality of work, and teamwork skills.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Hi there, Brian. It's time for our _ review. How's _ going?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`performance`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it refers to how well someone is doing their job. The review is a discussion about it.
|
||||
|
||||
---
|
||||
|
||||
`everything`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is a general inquiry about how all aspects of work or life are going, often used to start a conversation.
|
||||
@@ -0,0 +1,59 @@
|
||||
---
|
||||
id: 66122ab30afc8e2b1f42b78a
|
||||
title: Task 15
|
||||
challengeType: 22
|
||||
dashedName: task-15
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Things are going well. Last week, I worked on improving our project's documentation. I updated the user manual and added some FAQs based on customer feedback. I also attended the customer support training session.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`FAQ` stands for `Frequently Asked Questions`. It's a list of questions and answers about a particular topic, often found on websites or product manuals. For example, `The software's FAQ page helps users troubleshoot common issues.`
|
||||
|
||||
`Based on` is a phrase used to show that something is made using certain information or ideas. In tech, you might say, `This update is based on user suggestions.`
|
||||
|
||||
To `attend` means to go to or be present at an event or meeting. In a professional setting, `attending` training can mean participating in a session to learn new skills. For instance, `I attended a webinar on cybersecurity.`
|
||||
|
||||
These terms are commonly used in professional and technical contexts.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Things are going well. Last week, I worked _ improving our project's documentation. I updated the user manual and added some FAQs _ on customer feedback. I also _ the customer support _ session.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`on`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used to indicate the focus of the improvement, in this case, the project's documentation.
|
||||
|
||||
---
|
||||
|
||||
`based`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It indicates that the FAQs were created using the information gathered from customer feedback.
|
||||
|
||||
---
|
||||
|
||||
`attended`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means that Brian was present at or participated in an event, here referring to the training session.
|
||||
|
||||
---
|
||||
|
||||
`training`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to the session Brian attended, designed to teach or enhance skills, particularly in customer support.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 66122b7d6f1f182bb1fe0338
|
||||
title: Task 16
|
||||
challengeType: 19
|
||||
dashedName: task-16
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Things are going well. Last week, I worked on improving our project's documentation. I updated the user manual and added some FAQs based on customer feedback. I also attended the customer support training session.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
This task checks your comprehension of Brian's activities from last week.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What did Brian work on last week?
|
||||
|
||||
## --answers--
|
||||
|
||||
He developed a new software feature.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. Brian's focus was on documentation and training, not on developing new software features.
|
||||
|
||||
---
|
||||
|
||||
He focused on marketing and sales strategies.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's activities were related to documentation and training, not marketing and sales.
|
||||
|
||||
---
|
||||
|
||||
He improved project documentation and attended a training session.
|
||||
|
||||
---
|
||||
|
||||
He was on leave for personal reasons.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect as Brian mentioned actively working on project documentation and attending a training session.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
id: 661253cc9fb5ee2d01a0d6a8
|
||||
title: Task 17
|
||||
challengeType: 22
|
||||
dashedName: task-17
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: It helped me understand the issues our customers are facing, and I learned some strategies for better addressing their concerns.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`To address` means to deal with or handle a problem or challenge. In technology, for instance, you might say, `We need to address the bugs in our software.` meaning you need to find and fix the bugs.
|
||||
|
||||
`Concerns` are worries, problems, or issues that someone has. In a customer support context, a `concern` might be a difficulty a user is facing with a product. For example, `The main concern of our users is the app's loading speed.`
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`It helped me understand the issues our customers are facing, and I learned some _ for better _ their _.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`strategies`
|
||||
|
||||
### --feedback--
|
||||
|
||||
These are planned methods or approaches to solve a problem or achieve a goal.
|
||||
|
||||
---
|
||||
|
||||
`addressing`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means dealing with or handling, in this context, how to manage customers' issues effectively.
|
||||
|
||||
---
|
||||
|
||||
`concerns`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to the problems or challenges the customers are experiencing.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661254cf9474ed2da90fec1b
|
||||
title: Task 18
|
||||
challengeType: 19
|
||||
dashedName: task-18
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Things are going well. Last week, I worked on improving our project's documentation. I updated the user manual and added some FAQs based on customer feedback. I also attended the customer support training session. It helped me understand the issues our customers are facing, and I learned some strategies for better addressing their concerns.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
This task tests your comprehension of what helped Brian understand his customers' problems and what he learned in the process.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What helped Brian understand his customers' problems, and what did he learn?
|
||||
|
||||
## --answers--
|
||||
|
||||
Updating the user manual helped him, and he learned about the new software features.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. While updating the user manual was part of his work, it was the training session that helped him understand customer issues and learn new strategies.
|
||||
|
||||
---
|
||||
|
||||
Attending the customer support training session helped him, and he learned strategies for addressing customer concerns.
|
||||
|
||||
---
|
||||
|
||||
Creating FAQs based on customer feedback helped him, and he learned how to design better user interfaces.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Creating FAQs was part of Brian's work, but it was specifically the training session that provided insights into customer issues and strategies.
|
||||
|
||||
---
|
||||
|
||||
Working on the project documentation helped him, and he learned about project management.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect as it was the training session, not just working on documentation, that helped Brian gain insights into customer issues.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
id: 66125530a1a9e92e0e08d594
|
||||
title: Task 19
|
||||
challengeType: 22
|
||||
dashedName: task-19
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Maria: Excellent. Learning more about our customers is essential. I appreciate your dedication. Can you tell me about your long-term goals?
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
In this task, you'll learn the differences between `short-term`, `mid-term`, and `long-term` goals.
|
||||
|
||||
`Short-term` goals are objectives you plan to achieve soon, usually within a few days to a year. For example, `Finishing a report by the end of the week` is a `short-term` goal.
|
||||
|
||||
`Mid-term` goals are targets set for a slightly longer period, often between a year and five years. An example might be, `Getting a professional certification in the next two years`.
|
||||
|
||||
`Long-term` goals are plans that are expected to be achieved over a more extended period, typically five years or more. For instance, `Becoming a team leader in ten years` is a `long-term` goal.
|
||||
|
||||
Understanding these time frames helps in setting realistic and achievable objectives in both personal and professional contexts.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`_. Learning more about our customers is essential. I _ your _. Can you tell me about your _ goals?`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Excellent`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used by Maria to positively acknowledge the information shared. This word is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`appreciate`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It indicates that Maria values and is thankful for the effort shown.
|
||||
|
||||
---
|
||||
|
||||
`dedication`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to the commitment and hard work shown.
|
||||
|
||||
---
|
||||
|
||||
`long-term`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it refers to goals that are planned to be achieved over an extended period.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661255c3b6ea612e984a62b8
|
||||
title: Task 20
|
||||
challengeType: 19
|
||||
dashedName: task-20
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Maria: Excellent. Learning more about our customers is essential. I appreciate your dedication. Can you tell me about your long-term goals?
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
This task assesses your understanding of Maria's perspective.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Maria emphasize and ask about in her statement to Brian?
|
||||
|
||||
## --answers--
|
||||
|
||||
She emphasizes the importance of team collaboration and asks about Brian's team management skills.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. Maria focuses on customer knowledge and inquires about Brian's long-term goals, not team management.
|
||||
|
||||
---
|
||||
|
||||
She stresses the need for immediate results and asks about Brian's weekly tasks.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Maria's statement is about the importance of understanding customers and long-term goals, not immediate results or weekly tasks.
|
||||
|
||||
---
|
||||
|
||||
She highlights the importance of learning about customers and asks about Brian's long-term goals.
|
||||
|
||||
---
|
||||
|
||||
She appreciates Brian's technical skills and asks about his recent project achievements.
|
||||
|
||||
### --feedback--
|
||||
|
||||
While Maria appreciates Brian's dedication, her focus is on understanding customers and inquiring about his long-term goals, not his technical skills or recent projects.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
@@ -0,0 +1,41 @@
|
||||
---
|
||||
id: 66125666f8437c2f3616045e
|
||||
title: Task 21
|
||||
challengeType: 22
|
||||
dashedName: task-21
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Of course. By the end of the quarter, I plan to have the documentation I’m working on fully updated, and I intend to improve our customer support process based on the training I received.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
A `quarter` divides the year into four equal parts, each consisting of three months.
|
||||
|
||||
The `first quarter` (Q1) covers January to March, the `second quarter` (Q2) spans April to June, the `third quarter` (Q3) includes July to September, and the `fourth quarter` (Q4) encompasses October to December.
|
||||
|
||||
For example, in business, a company might review its sales at the end of each `quarter`. A tech team might have a goal to release a new software update by the end of Q2.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Of course. By the end of the _, I plan to have the documentation I’m working on fully updated, and I _ to improve our customer support process based on the training I received.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`quarter`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to one-fourth of the year. Brian's goal is to complete his tasks by the end of this period.
|
||||
|
||||
---
|
||||
|
||||
`intend`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means to have a plan or aim. Brian is planning to enhance the customer support process.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661256fe823f142fb9858beb
|
||||
title: Task 22
|
||||
challengeType: 19
|
||||
dashedName: task-22
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Of course. By the end of the quarter, I plan to have the documentation I’m working on fully updated, and I intend to improve our customer support process based on the training I received.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Brian plan to accomplish by the end of the quarter?
|
||||
|
||||
## --answers--
|
||||
|
||||
Starting a new project from scratch
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect. Brian's focus is on updating existing documentation and improving customer support, not starting a new project.
|
||||
|
||||
---
|
||||
|
||||
Updating the project documentation and improve customer support
|
||||
|
||||
---
|
||||
|
||||
Attending more training sessions
|
||||
|
||||
### --feedback--
|
||||
|
||||
While training has influenced his plans, Brian's main goal is to update documentation and enhance customer support, not just attend training.
|
||||
|
||||
---
|
||||
|
||||
Organizing team meetings
|
||||
|
||||
### --feedback--
|
||||
|
||||
Organizing meetings is not mentioned; his plans are centered around documentation and customer support improvements.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 66126744e24b0a31255718a7
|
||||
title: Task 23
|
||||
challengeType: 19
|
||||
dashedName: task-23
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Of course. By the end of the quarter, I plan to have the documentation I’m working on fully updated, and I intend to improve our customer support process based on the training I received.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Practice time!
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
Why does Brian intend to improve the customer support process?
|
||||
|
||||
## --answers--
|
||||
|
||||
He received complaints from customers.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect as Brian's motivation for improving customer support is based on training, not directly on customer complaints.
|
||||
|
||||
---
|
||||
|
||||
It's a routine quarterly goal.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The routine aspect is not mentioned; his intention is specifically linked to the insights gained from training.
|
||||
|
||||
---
|
||||
|
||||
Based on the training he received.
|
||||
|
||||
---
|
||||
|
||||
He wants to increase sales.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Increasing sales is not mentioned; his focus is on enhancing support due to his recent training.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
@@ -0,0 +1,51 @@
|
||||
---
|
||||
id: 661267c5ac355931ab1f933d
|
||||
title: Task 24
|
||||
challengeType: 22
|
||||
dashedName: task-24
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Maria: It sounds like you're on the right track. Keep up the good work, and don't hesitate to reach out if you need any support.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Being `on the right track` means going in the right direction or making good progress. For instance, in a project, if things are going as planned, you can say, `We are on the right track.`
|
||||
|
||||
To `hesitate` means to pause or hold back in uncertainty. In a work context, `Don't hesitate to ask for help` means you shouldn't be afraid or unsure about asking for assistance.
|
||||
|
||||
`Reach out` means to contact someone for help or information. For example, `If you have any questions, reach out to the tech support team.`
|
||||
|
||||
These expressions are commonly used in professional environments to encourage ongoing progress and open communication.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`It sounds like you're on the right _. Keep up the good work, and don't _ to reach _ if you need any support.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`track`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to a path or course of action. It's used here to affirm that someone is making good progress or heading in the correct direction.
|
||||
|
||||
---
|
||||
|
||||
`hesitate`
|
||||
|
||||
### --feedback--
|
||||
|
||||
This verb means to pause before saying or doing something because you are uncertain, nervous, or not sure how to proceed.
|
||||
|
||||
---
|
||||
|
||||
`out`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It suggests making an effort to contact or communicate with someone.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 6612693507cbd43269ae64e0
|
||||
title: Task 25
|
||||
challengeType: 19
|
||||
dashedName: task-25
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Maria: It sounds like you're on the right track. Keep up the good work, and don't hesitate to reach out if you need any support.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Recognizing words of encouragement and offers of assistance is crucial in professional communication, as they contribute to a supportive work environment.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What is Maria expressing to Brian in her statement?
|
||||
|
||||
## --answers--
|
||||
|
||||
She is unhappy with Brian's progress and demands immediate improvement.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This choice is incorrect. Maria's words are supportive and encouraging, not critical.
|
||||
|
||||
---
|
||||
|
||||
Maria is encouraging Brian, appreciating his efforts, and offering support if needed.
|
||||
|
||||
---
|
||||
|
||||
She is instructing Brian to change his work approach completely.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Maria's statement does not suggest a complete change in work approach; instead, it encourages the current direction.
|
||||
|
||||
---
|
||||
|
||||
Maria is asking Brian for a detailed report on his work.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The focus of Maria's message is encouragement and support, not requesting a detailed report.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
id: 661269c4ccdd4132db7517b8
|
||||
title: Task 26
|
||||
challengeType: 22
|
||||
dashedName: task-26
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Thanks, Maria. I appreciate your guidance.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Fill in the blank in the dialogue below.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Thanks, Maria. I appreciate your _.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`guidance`
|
||||
|
||||
### --feedback--
|
||||
|
||||
In this context, it refers to the advice, support, or direction that Maria has provided to Brian.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 66126a21821998335a86a34b
|
||||
title: Task 27
|
||||
challengeType: 22
|
||||
dashedName: task-27
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Entire dialogue
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the dialogue and fill in the blanks with the correct words.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`In their performance review, Brian reports his progress on the project's _, discusses his _ to enhance customer support, and outlines his _ goals. Maria responds with encouragement and _ to provide support.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`documentation`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to the project materials Brian has been updating.
|
||||
|
||||
---
|
||||
|
||||
`intention`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It highlights Brian's plan to improve the customer support process.
|
||||
|
||||
---
|
||||
|
||||
`long-term`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It describes the type of goals Brian is setting for the future.
|
||||
|
||||
---
|
||||
|
||||
`offers`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to Maria's willingness to provide assistance and support.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
id: 66127192c932be37ed0217e7
|
||||
title: "Dialogue 3: Sharing Accomplishments over Lunch"
|
||||
challengeType: 21
|
||||
dashedName: dialogue-3-sharing-accomplishments-over-lunch
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video below to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661271c2b16aff3870604148
|
||||
title: Task 28
|
||||
challengeType: 19
|
||||
dashedName: task-28
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: Hey, Sarah! It's been a while since we hung out like this.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
When people say `it's been a while`, they mean a long time has passed between today and the last time something happened.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
How long has it been since Brian and Sarah last hung out together?
|
||||
|
||||
## --answers--
|
||||
|
||||
It's been a long time.
|
||||
|
||||
---
|
||||
|
||||
They met just recently.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's statement `been a while` indicates that their last meeting wasn't recent.
|
||||
|
||||
---
|
||||
|
||||
They have never hung out before.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's reference to `like this` suggests they have hung out before, contradicting the idea that they never met in this way.
|
||||
|
||||
---
|
||||
|
||||
They meet regularly.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's phrase implies that their meetings are not regular.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 6612727ec0a11b390b8e92cb
|
||||
title: Task 29
|
||||
challengeType: 19
|
||||
dashedName: task-29
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Hey! Work has kept me busy this week.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`Has kept` is used to describe an ongoing action or state that started in the past and continues into the present. For example, `The training has kept me engaged.` means the training started in the past and is still engaging the person now.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Sarah mean?
|
||||
|
||||
## --answers--
|
||||
|
||||
She started a new job this week.
|
||||
|
||||
### --feedback--
|
||||
|
||||
This option is incorrect as Sarah's statement refers to ongoing work keeping her busy, not starting a new job.
|
||||
|
||||
---
|
||||
|
||||
She has been busy with work throughout the week.
|
||||
|
||||
---
|
||||
|
||||
She is planning to take on more work soon.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah's statement is about her current workload, not about future plans to increase it.
|
||||
|
||||
---
|
||||
|
||||
She had a lot of free time this week.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The phrase `has kept me busy` implies that Sarah had little free time, not a lot.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
id: 6612752978bcc239ae7b60da
|
||||
title: Task 30
|
||||
challengeType: 22
|
||||
dashedName: task-30
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Hey! Work has kept me busy this week. I worked on the new app interface, designed some cool icons, and presented the layout to the team yesterday.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
This task will help you practice identifying verbs in the past simple tense.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Hey! Work has kept me busy this week. I _ on the new app interface, _ some cool icons, and _ the layout to the team yesterday.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`worked`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `work`, indicating an action completed in the past.
|
||||
|
||||
---
|
||||
|
||||
`designed`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `design`, used to describe a completed action of creating something.
|
||||
|
||||
---
|
||||
|
||||
`presented`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `present`, indicating the action of showing or displaying something that has already been done.
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
id: 6612757ffdc16b3a22b08427
|
||||
title: Task 31
|
||||
challengeType: 22
|
||||
dashedName: task-31
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: That sounds awesome! I tested the app for bugs. We found a few, but the good news is we fixed them all. It seems pretty solid now.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`That sounds awesome! I _ the app for bugs. We _ a few, but the good news is we _ them all. It seems pretty solid now.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`tested`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `test`, indicating an action that was completed in the past.
|
||||
|
||||
---
|
||||
|
||||
`found`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `find`, used here to describe the discovery of bugs which occurred in the past.
|
||||
|
||||
---
|
||||
|
||||
`fixed`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `fix`, indicating the completed action of resolving the found bugs.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 6612762a058bb43b960e91ca
|
||||
title: Task 32
|
||||
challengeType: 19
|
||||
dashedName: task-32
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: That sounds awesome! I tested the app for bugs. We found a few, but the good news is we fixed them all. It seems pretty solid now.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What did Brian and his team do with the app?
|
||||
|
||||
## --answers--
|
||||
|
||||
They added new features to the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's focus was on testing for bugs and fixing them, not adding new features.
|
||||
|
||||
---
|
||||
|
||||
They tested the app, found bugs, and fixed them.
|
||||
|
||||
---
|
||||
|
||||
They only discussed potential improvements for the app.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's statement goes beyond discussion; it involves active testing and fixing of bugs.
|
||||
|
||||
---
|
||||
|
||||
They prepared the app for a major launch.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Preparing for a launch isn't mentioned. Brian's update is about testing and fixing bugs in the app.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,57 @@
|
||||
---
|
||||
id: 66127678c88f183c0312d8e8
|
||||
title: Task 33
|
||||
challengeType: 19
|
||||
dashedName: task-33
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: It seems pretty solid now.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
The expression `It seems pretty solid now` indicates the current status or quality of a project, common in professional and technical discussions.
|
||||
|
||||
When something is described as `pretty solid`, it means it is very good, reliable, or strong in quality. It's a way of saying that something is dependable and performs well.
|
||||
|
||||
For example, if someone says, `The plan for the weekend is pretty solid`, they mean that the plan is well-thought-out, reliable, and likely to be successful or enjoyable.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What does Brian imply about the app?
|
||||
|
||||
## --answers--
|
||||
|
||||
The app is likely unstable and needs more work.
|
||||
|
||||
### --feedback--
|
||||
|
||||
`Pretty solid` suggests reliability and stability, not instability.
|
||||
|
||||
---
|
||||
|
||||
The app is functioning well and is reliable after fixing the bugs.
|
||||
|
||||
---
|
||||
|
||||
The app has not been tested thoroughly yet.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's statement implies that after testing and fixing, the app is now in a good state, contradicting the idea of insufficient testing.
|
||||
|
||||
---
|
||||
|
||||
The app will be redesigned entirely.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Redesigning the app is not implied in Brian's statement about its current solid state.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,45 @@
|
||||
---
|
||||
id: 66127755a52efa3c9a73065b
|
||||
title: Task 34
|
||||
challengeType: 22
|
||||
dashedName: task-34
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Nice work! I also attended a UX design workshop last month. I learned some great techniques for user research. I've applied them to our project, and it helped improve the user experience.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and complete the sentence.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Nice work! I also _ a UX design workshop last month. I _ some great techniques for user research. I've applied them to our project, and it _ improve the user experience.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`attended`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `attend`, showing that Sarah participated in the workshop.
|
||||
|
||||
---
|
||||
|
||||
`learned`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `learn`, indicating that Sarah gained new knowledge.
|
||||
|
||||
---
|
||||
|
||||
`helped`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `help`, showing that the application of new techniques had a positive effect.
|
||||
@@ -0,0 +1,47 @@
|
||||
---
|
||||
id: 661277970c67233d02f138de
|
||||
title: Task 35
|
||||
challengeType: 22
|
||||
dashedName: task-35
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Nice work! I also attended a UX design workshop last month. I learned some great techniques for user research. I've applied them to our project, and it helped improve the user experience.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`UX` stands for User Experience. It refers to how a person feels when they are using a product, system, or service. This includes websites, apps, and electronic devices. A `UX designer` makes things easy and nice for people to use on the computer or phone.
|
||||
|
||||
For example: `The UX of this website is excellent because it's easy to navigate and find the information you need.`
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`Nice work! I also attended a _ design workshop last month. I learned some great _ for user research. I've applied them to our project, and it helped _ the user experience.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`UX`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It stands for User Experience, a key aspect of design focusing on how users interact with products.
|
||||
|
||||
---
|
||||
|
||||
`techniques`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to methods or ways of doing something, in this case, for conducting user research.
|
||||
|
||||
---
|
||||
|
||||
`improve`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It means to make something better, here referring to enhancing the user experience of the project.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661278160653ee3d9040ed68
|
||||
title: Task 36
|
||||
challengeType: 19
|
||||
dashedName: task-36
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Nice work! I also attended a UX design workshop last month. I learned some great techniques for user research. I've applied them to our project, and it helped improve the user experience.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the audio and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What did Sarah do last month?
|
||||
|
||||
## --answers--
|
||||
|
||||
She started a new project on user experience.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah's focus was on attending a workshop and learning new techniques, not starting a new project.
|
||||
|
||||
---
|
||||
|
||||
She took a vacation.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Taking a vacation is not mentioned; Sarah's statement was about attending a UX design workshop.
|
||||
|
||||
---
|
||||
|
||||
She attended a UX design workshop and learned user research techniques.
|
||||
|
||||
---
|
||||
|
||||
She was promoted to a new position.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Sarah's statement revolves around attending a workshop and learning, not about a job promotion.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
3
|
||||
@@ -0,0 +1,63 @@
|
||||
---
|
||||
id: 66127850c4415c3df1b4e99a
|
||||
title: Task 37
|
||||
challengeType: 22
|
||||
dashedName: task-37
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: That's impressive. I met with the client yesterday, and they loved our progress. They gave us the green light to move on to the next phase.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
In this task, you'll learn about the phrase `to give the green light to something`. This phrase means to give permission or approval to proceed with a project or plan.
|
||||
|
||||
For example, in a work setting, a manager might say, `We've been given the green light to start the new marketing campaign.` indicating that they have approval to begin.
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`That's impressive. I _ with the client _, and they _ our progress. They _ us the green light to move _ to the next phase.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`met`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past simple form of `meet`, indicating that Brian had a meeting with the client.
|
||||
|
||||
---
|
||||
|
||||
`yesterday`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It refers to the day before today, specifying when the meeting took place.
|
||||
|
||||
---
|
||||
|
||||
`loved`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past tense of `love`, used here to show that the client was very pleased with the progress.
|
||||
|
||||
---
|
||||
|
||||
`gave`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is the past tense of `give`. In this context, it refers to the client giving approval.
|
||||
|
||||
---
|
||||
|
||||
`on`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It indicates progressing or advancing to the next stage or phase of a project.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 6612792bc77de13e8f2af3ad
|
||||
title: Task 38
|
||||
challengeType: 19
|
||||
dashedName: task-38
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Brian: That's impressive. I met with the client yesterday, and they loved our progress. They gave us the green light to move on to the next phase.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
This task tests your understanding of Brian's activities on the previous day. Comprehending recent events and their outcomes is important in professional settings, as they can influence project direction and team morale.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What happened to Brian yesterday?
|
||||
|
||||
## --answers--
|
||||
|
||||
He worked on a new project proposal.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's statement was about meeting with the client and discussing the current project's progress, not about working on a new proposal.
|
||||
|
||||
---
|
||||
|
||||
He met with the client who approved the project's progress.
|
||||
|
||||
---
|
||||
|
||||
He conducted a team meeting to plan the next phase.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Brian's focus was on a client meeting, not on conducting a team meeting.
|
||||
|
||||
---
|
||||
|
||||
He resolved technical issues in the project.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Fixing technical issues isn't mentioned; the focus was on a client meeting where they expressed satisfaction with the project's progress.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
2
|
||||
@@ -0,0 +1,39 @@
|
||||
---
|
||||
id: 6612797faf03663ef83f4459
|
||||
title: Task 39
|
||||
challengeType: 22
|
||||
dashedName: task-39
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Sarah: Way to go! It looks like we’re making great progress.
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
`Way to go` is an informal way of congratulating someone or showing approval for their success or progress. It's like saying "well done" or "good job".
|
||||
|
||||
For example, in a work context, if a team member completes a challenging task, you might say, `Way to go on finishing that report!`
|
||||
|
||||
# --fillInTheBlank--
|
||||
|
||||
## --sentence--
|
||||
|
||||
`_ to go! It looks like _ making great progress.`
|
||||
|
||||
## --blanks--
|
||||
|
||||
`Way`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is used here as part of an expression of congratulations or approval for good work or progress. This word is capitalized.
|
||||
|
||||
---
|
||||
|
||||
`we're`
|
||||
|
||||
### --feedback--
|
||||
|
||||
It is a contraction of `we are`, indicating the ongoing action of making progress by the team.
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
id: 661279c8d3bf0f3f6f23f21f
|
||||
title: Task 40
|
||||
challengeType: 19
|
||||
dashedName: task-40
|
||||
---
|
||||
|
||||
<!--
|
||||
AUDIO REFERENCE:
|
||||
Entire dialogue
|
||||
-->
|
||||
|
||||
# --description--
|
||||
|
||||
Listen to the dialogue and answer the question.
|
||||
|
||||
# --question--
|
||||
|
||||
## --text--
|
||||
|
||||
What is the summary of Brian and Sarah's conversation?
|
||||
|
||||
## --answers--
|
||||
|
||||
They discussed their work, a UX design workshop, and client meetings.
|
||||
|
||||
---
|
||||
|
||||
They talked about starting a new project next week.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The conversation focused on their current work and achievements, not starting a new project.
|
||||
|
||||
---
|
||||
|
||||
They planned a team outing to discuss future strategies.
|
||||
|
||||
### --feedback--
|
||||
|
||||
The discussion was about their work and recent achievements, not about planning a team outing.
|
||||
|
||||
---
|
||||
|
||||
Brian and Sarah complained about their workload and lack of progress.
|
||||
|
||||
### --feedback--
|
||||
|
||||
Their conversation was positive, discussing their achievements and progress.
|
||||
|
||||
## --video-solution--
|
||||
|
||||
1
|
||||
@@ -1,15 +0,0 @@
|
||||
---
|
||||
id: 655cd38e0ee8668d87f50f82
|
||||
title: "Dialogue: Placeholder"
|
||||
challengeType: 21
|
||||
videoId: nLDychdBwUg
|
||||
dashedName: dialogue-placeholder
|
||||
---
|
||||
|
||||
# --description--
|
||||
|
||||
Watch the video above to understand the context of the upcoming lessons.
|
||||
|
||||
# --assignment--
|
||||
|
||||
Watch the video
|
||||
Reference in New Issue
Block a user