Align README with published Week 4 closing chapter - #227
Merged
Merged
Conversation
Replace stale 'open-ended collection of future optimizations' and '(TBD)' labels with wording that matches the new closing chapter's guided expansion paths.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
PR #226 replaced the empty Week 4 TBD table with a full closing chapter, but the README still says "open-ended collection of future optimizations" and "Optional optimizations (TBD)".
What changed
Two-line README-only fix: replaced stale descriptions with wording that matches the published closing chapter.
AI-Assisted: DeepSeek V4 Pro + Sentinel