Fix typos in _quantization_utils docstring/comment - #757
Closed
PratikDhanave wants to merge 1 commit into
Closed
Conversation
- 'In ths API' -> 'In this API' - 'limited to INT$ per-channel' -> 'INT4/INT8' (both are supported) - 'pre-trained checkpoitns' -> 'checkpoints' - 'are isntead under' -> 'are instead under'
Author
|
Superseded by #763, which bundles this typo fix with the other pure-typo fixes into a single PR. |
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.
Several typo fixes in
gemma/peft/_quantization_utils.py(docstring/comment only, no behavior change):In ths API->In this APIlimited to INT$ per-channel->limited to INT4/INT8 per-channel($is a garbled digit; bothINT4andINT8are supported byQuantizationMethod, so name both)pre-trained checkpoitns->pre-trained checkpointsare isntead under->are instead under