Skip to content

Corrected grammatical and typographical errors in cheat sheet #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jayathuc
Copy link

@jayathuc jayathuc commented Jul 1, 2024

Asymptotic Notation
Correction: "Big-O refers to the upper bound of time or space complexity of an algorithm, meaning it worst case runtime scenario."
Updated: "Big-O refers to the upper bound of time or space complexity of an algorithm, typically representing the worst-case runtime scenario."

Typo: "Best case means a ideal input."
Updated: "Best case means an ideal input."

Search Algorithms - Depth First Search
Correction: "It traverses left down a tree until it cannot go further."
Updated: "It traverses down the left side of a tree until it cannot go further."

Sorting Algorithms - Insertion Sort
Correction: "Although it has an O(n^2) time complexity, in practice it "is slightly less" since its comparison scheme only requires checking place if it is smaller than its neighbor."
Updated: "Although it has an O(n^2) time complexity, in practice it "can perform better" since its comparison scheme only requires checking place if it is smaller than its neighbor."

Sorting Algorithms - Merge Sort
Correction: "Worst Case: O(1)"
Updated: "Worst Case: O(n)" (because merge sort requires additional space proportional to the input size.)

- Updated Big-O definition in Asymptotic Notation section
- Corrected "ideal input" typo in Best Case definition
- Improved DFS traversal description in Search Algorithms section
- Clarified Insertion Sort performance description
- Fixed Merge Sort worst-case space complexity

This commit addresses minor issues to improve readability and accuracy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant