During May 2025, Tievens enhanced the moq-wg/moq-transport repository by clarifying protocol terminology to improve integration clarity and reduce client confusion. Focusing on documentation, Tievens updated Markdown files to standardize the use of "Joining Request ID" across FETCH messages and error codes, replacing previous inconsistent terms. This work involved careful revision of message descriptions and error nomenclature, ensuring that the protocol’s internal language aligned with intended client interactions. By maintaining existing behavior and avoiding public API changes, Tievens prioritized maintainability and onboarding efficiency. The depth of the work lay in its attention to detail and its impact on integration reliability.