Clarify numeric literal terminology in data types section #4339
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.
This PR enhances clarity in the "Integer Literals" documentation section by:
Acknowledging the intentional shift from "integer literals" to "number literals"
Explicitly connecting numeric literal features to floating-point literals
Maintaining table accuracy while explaining broader applicability
The changes help readers understand that type suffixes and visual separators apply to all numeric literals, while keeping the section focused on integer examples.