zama-ai
fix: typos and improve clarity in documentation
Description:
This pull request corrects several typos and improves the clarity of the documentation across multiple files. Minor wording adjustments were made to enhance readability and maintain consistency.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
![cla-bot[bot] avatar](https://avatars.githubusercontent.com/in/2404?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
Thank you for your pull request. We require contributors to sign our Contributor License Agreement / Terms and Conditions, and we don't seem to have the users @kilavvy on file. In order for us to review and merge your code, please sign:
- For individual contribution: our CLA
- for Bounty submission, if you are an individual: our T&C
- for Bounty submission, if you are a company: our T&C to get yourself added.
If you already signed one of this document, just wait to be added to the bot config.
hey @kilavvy, thanks for your PR, it's currently blocked because commit messages are not matching the regexp,
could you please squash all commits into one single commit with a first line similar to: chore(common): fix typos?
Cannot merge because of comitlint:
⧗ input: chore: Update README.md ✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
change commit to:
docs(common): message
