Skip to content

Fix typos in Getting Started With KerasHub#2235

Open
darmendariz wants to merge 1 commit intokeras-team:masterfrom
darmendariz:fix-typos-in-keras_hub-getting-started
Open

Fix typos in Getting Started With KerasHub#2235
darmendariz wants to merge 1 commit intokeras-team:masterfrom
darmendariz:fix-typos-in-keras_hub-getting-started

Conversation

@darmendariz
Copy link

Noticed a few minor typos while reading the KerasHub Getting Started Guide. Per the keras-io ReadMe (Fixing Typos), I made the same edits in the corresponding .py, .ipynb, and .md files.

@google-cla
Copy link

google-cla bot commented Jan 9, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @darmendariz, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refines the 'Getting Started With KerasHub' guide by addressing various textual and formatting inconsistencies across its Jupyter Notebook, Python script, and Markdown versions. The changes aim to enhance the clarity, accuracy, and overall professional presentation of the documentation, providing a more polished and error-free learning resource for users.

Highlights

  • Grammar and Spelling Corrections: Multiple grammatical errors, such as 'an Kaggle' to 'a Kaggle' and 'Arrow indicate' to 'Arrows indicate', have been corrected. Several spelling mistakes, including 'AudioConveter' to 'AudioConverter', 'contrains' to 'contains', 'traininable' to 'trainable', and 'well upload' to 'will upload', have also been fixed.
  • Redundancy and Punctuation: Redundant words like 'with' in 'preprocessing with will resize' have been removed, and minor punctuation issues, such as an unnecessary comma in 'Kaggle to, download', have been resolved.
  • Typographic Consistency: Unicode typographic dashes (\u2014) have been standardized to the more common em dash () for improved readability.
  • Formatting Cleanup: Minor formatting adjustments, including the removal of trailing empty lines in code blocks and the 'No newline at end of file' marker, have been applied to ensure cleaner file structures.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request fixes several typos across the KerasHub getting started guide in the notebook, Python, and Markdown files. The changes are correct and improve the readability of the documentation. I've found one additional minor issue in the description of AudioConverter that seems to be a copy-paste error, which I've commented on. Overall, great work on catching these typos and ensuring consistency across the different file formats!

" preprocessing.\n",
" * **Inherits from**: `keras.layers.Layer`.\n",
"* **AudioConveter**: `keras_hub.layers.AudioConveter`.\n",
"* **AudioConverter**: `keras_hub.layers.AudioConverter`.\n",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Thanks for correcting the AudioConverter typo. While reviewing, I noticed a small copy-paste error in the description for this class on line 176. It says it 'encapsulates the image specific preprocessing', which seems incorrect for an audio converter. It should likely be 'audio specific preprocessing'. Would you mind fixing that as well?

preprocessing.
* **Inherits from**: `keras.layers.Layer`.
* **AudioConveter**: `keras_hub.layers.AudioConveter`.
* **AudioConverter**: `keras_hub.layers.AudioConverter`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Thanks for correcting the AudioConverter typo. While reviewing, I noticed a small copy-paste error in the description for this class on line 123. It says it 'encapsulates the image specific preprocessing', which seems incorrect for an audio converter. It should likely be 'audio specific preprocessing'. Would you mind fixing that as well?

preprocessing.
* **Inherits from**: `keras.layers.Layer`.
* **AudioConveter**: `keras_hub.layers.AudioConveter`.
* **AudioConverter**: `keras_hub.layers.AudioConverter`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Thanks for correcting the AudioConverter typo. While reviewing, I noticed a small copy-paste error in the description for this class on line 121. It says it 'encapsulates the image specific preprocessing', which seems incorrect for an audio converter. It should likely be 'audio specific preprocessing'. Would you mind fixing that as well?

@darmendariz darmendariz force-pushed the fix-typos-in-keras_hub-getting-started branch from d03b888 to 4ef6574 Compare January 16, 2026 17:21
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.

2 participants