Back to Freecodecamp

Task 145

curriculum/challenges/english/blocks/learn-how-to-clarify-misunderstandings/67f3ca5863fa8f015ee736d9.md

latest1.9 KB
Original Source
<!-- READING -->

--instructions--

Read the text and answer the question below.

--questions--

--text--

After their conversation, Jessica followed up with an email to confirm the project details and share the updated timeline:

Hi David,

As promised, here's the updated project timeline for the finance app, including more detail on where things stand:

April 8–9: Final bug fixes focused on minor user interface glitches discovered after main testing.

April 10: Quick round of regression testing to confirm all issues are resolved and nothing new has appeared.

April 11: Release preparation — packaging the build, updating documentation, and internal review.

April 12: App launch as planned.

We're still on schedule, and no major blockers have come up. Just to clarify, all core features are stable and performing well. The budget tracking feature is confirmed for the next release, which we're planning for later this month. I'll follow up soon with that timeline once it's finalized.

Let me know if there's anything else you'd like to go over.

Thanks,

Jessica

Why does Jessica mention the budget tracking feature in the email?

--answers--

To explain it is already included in the current release.

--feedback--

Jessica clearly states that it is scheduled for the next release, not the current one.


To inform David that it will not be developed.

--feedback--

She doesn't say it's canceled.


To clarify that it was a mix-up and confirm it's in the next update.


To request David to review it again.

--feedback--

Jessica does not ask David to review anything related to that feature.

--video-solution--

3

--explanation--

To find the correct answer, focus on the part where Jessica explains the budget tracking feature.

She clarifies that the feature is not included in this release and is planned for the next update.

Look for the option that specifically addresses this clarification.