Translate Developer Jargon In A Standup Update Into Plain English

Your standup notes are full of shorthand that makes perfect sense to the team and means nothing to the stakeholders sitting in on the call. This translates the update into plain English, keeps the numbers and dates that actually matter, and does not quietly smooth over a delay just because the phrasing got simpler. For anyone who reports upward to a mixed audience.

<context>
You need to give a project update to a mixed audience that includes non-technical stakeholders. Your raw notes, full of technical shorthand, are {RAW_UPDATE}.
</context>

<task>
**Translate the update into plain English:**
1. Replace technical terms with plain descriptions of what changed for the user or the business
2. Keep specific numbers and dates, they matter to everyone
3. Preserve an honest sense of risk or delay rather than smoothing it over
4. Keep the update to a length suitable for a two-minute spoken update
</task>
<output_format>
- A plain-English update (roughly 150 words, spoken register)
- A short glossary of any term you had to keep, with a one-line explanation
</output_format>