docs: Fix typos and linguistic errors in documentation / hacktoberfest #343
Conversation
Signed-off-by: Sebastien Dionne <survivant00@gmail.com>
Summary of ChangesHello @survivant, 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 focuses on enhancing the overall quality and readability of the project's documentation and code comments. It addresses various typos, grammatical inconsistencies, and phrasing issues to make the information clearer and more professional for users and developers alike, contributing to a more polished user experience. Highlights
Using Gemini Code AssistThe 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
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 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
|
survivant
changed the title
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request does a great job of fixing various typos and linguistic errors throughout the documentation and code comments, improving overall readability. I've added a couple of suggestions to further enhance the clarity of the documentation in README.md and a Javadoc comment in A2ACardResolver.java. Thank you for the contribution!
http-client/src/main/java/io/a2a/client/http/A2ACardResolver.java
Outdated
Show resolved
Hide resolved
|
if you want can you add this label to this PR : hacktoberfest-accepted :) |
|
I'm just not sure with the "Gemini suggestions", I'll wait for a reviewer to validate if I should accept them. |
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
fjuma
left a comment
fjuma
left a comment
There was a problem hiding this comment.
Thanks very much @survivant!
a2aproject#343) # Description Fix typos and linguistic errors in documentation. It's not much but I'm happy to help Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [X ] Follow the [`CONTRIBUTING` Guide](../CONTRIBUTING.md). - [X ] Make your Pull Request title in the <https://www.conventionalcommits.org/> specification. - Important Prefixes for [release-please](https://github.com/googleapis/release-please): - `fix:` which represents bug fixes, and correlates to a [SemVer](https://semver.org/) patch. - `feat:` represents a new feature, and correlates to a SemVer minor. - `feat!:`, or `fix!:`, `refactor!:`, etc., which represent a breaking change (indicated by the `!`) and will result in a SemVer major. - [ X] Ensure the tests pass - [X ] Appropriate READMEs were updated (if necessary) Fixes #<issue_number_goes_here> 🦕 --------- Signed-off-by: Sebastien Dionne <survivant00@gmail.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
3 participants
Description
Fix typos and linguistic errors in documentation. It's not much but I'm happy to help
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
CONTRIBUTINGGuide.fix:which represents bug fixes, and correlates to a SemVer patch.feat:represents a new feature, and correlates to a SemVer minor.feat!:, orfix!:,refactor!:, etc., which represent a breaking change (indicated by the!) and will result in a SemVer major.Fixes #<issue_number_goes_here> 🦕