fixes from feedback

Author: thecraftman

CONTRIBUTING.md

@@ -27,11 +27,11 @@ When reporting a bug, please try and provide as much context as possible such as
 
 ## Submitting Modifications
 
-1. It's generally best to start by opening a new issue describing the bug or feature you're intending to fix. Even if you think it's relatively minor, it's helpful to know what people are working on. Mention in the initial issue that you are planning to work on that bug or feature so that it can be assigned to you.
+1. It's generally best to start by opening a new issue describing the bug or feature you intend to fix. Even if you think it's relatively minor, it's helpful to know what people are working on. Mention in the initial issue that you are planning to work on that bug or feature so that it can be assigned to you.
 
-2. Follow the normal process of [forking](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the project, and setup a new branch to work in. It's important that each group of changes be done in separate branches in order to ensure that a pull request only includes the commits related to that bug or feature.
+2. Follow the normal process of [forking](https://docs.github.com/en/get-started/quickstart/fork-a-repo) the project, and setup a new branch to work in. Each group of change must be done in separate branches in order to ensure that a pull request only includes the commits related to that bug or feature.
 
-3. Do your best to have [well-formated commit messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) for each change. This provides consistency throughout the project and ensures that commit messages are able to be formatted properly by various git tools.
+3. Do your best to have [well-formated commit messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html) for each change. This provides consistency throughout the project and ensures that commit messages can be adequately formatted by various git tools.
 
 4. Finally, push the commits to your fork and submit a [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)
 

README.md

@@ -104,12 +104,12 @@ run: /ops/main
 
 ## Documentation 
 
-- You can find the CTO.ai and CTO.ai Go SDK documentation [on the docs website](https://cto.ai/docs/golang-sdk-overview)
+- You can find the CTO.ai Go SDK documentation [on the docs website](https://cto.ai/docs/golang-sdk-overview)
 
 
 ## Contributing 
 
-The main aim of this repository is to continue developing and advancing CTO.ai Go, making it faster and more simplified to use. Kindly check our [contributing guide](https://github.com/cto-ai/sdk-go/blob/master/CONTRIBUTING.md) on how to propose bugfixes and improvements, and submitting pull requests to the project.
+The main aim of this repository is to continue developing and advancing CTO.ai Go, making it faster and more simplified to use. Kindly check our [contributing guide](https://github.com/cto-ai/sdk-go/blob/master/CONTRIBUTING.md) on how to propose bug fixes and improvements, as well as submit pull requests to the project.
 
 
 ## License