diff --git a/docs/CIP_2_Auth_Providers_Proposal.md b/docs/CIP_2_Auth_Providers_Proposal.md
index 95df2d9b6c3..6bc437a1e94 100644
--- a/docs/CIP_2_Auth_Providers_Proposal.md
+++ b/docs/CIP_2_Auth_Providers_Proposal.md
@@ -7,7 +7,7 @@ Current Status: `Accepted`
 ## **Motivation**
 
 Currently, Chroma does not provide any authentication mechanism. This CIP proposes to
-to add authentication abstractions and basic authentication mechanisms to Chroma.
+add authentication abstractions and basic authentication mechanisms to Chroma.
 
 There are intrinsic and extrinsic motivations for this CIP. The intrinsic motivation
 is to provide a secure way to access Chroma as adoption grows and the team is gearing up to release a cloud offering.
@@ -39,7 +39,7 @@ Request Sequence:
 
 ### Constraints
 
-This section provides teh architectural constraints for the authentication framework. The constraints are set of
+This section provides the architectural constraints for the authentication framework. The constraints are set of
 restrictions we impose to make the design simpler and more robust.
 
 - There must be at most one active client-side auth provider
@@ -168,7 +168,7 @@ Further work:
 
 ## **Compatibility, Deprecation, and Migration Plan**
 
-This change, introducing a pluggable auth framework is no impacting compatibility of existing deployments and users can
+This change, introducing a pluggable auth framework is not impacting compatibility of existing deployments and users can
 upgrade and use the new framework without the need for migration.
 
 No deprecations.
diff --git a/docs/CIP_Chroma_Improvment_Proposals.md b/docs/CIP_Chroma_Improvment_Proposals.md
index ce85c3fd623..13d4fa5096d 100644
--- a/docs/CIP_Chroma_Improvment_Proposals.md
+++ b/docs/CIP_Chroma_Improvment_Proposals.md
@@ -1,4 +1,4 @@
-# CIP Chroma Improvment Proposals
+# CIP Chroma Improvement Proposals
 
 ## Purpose
 
@@ -10,7 +10,7 @@ with it going forward.
 This means when making this kind of change we need to think through what we are doing as
 best we can prior to release. And as we go forward we need to stick to our decisions as
 much as possible. All technical decisions have pros and cons so it is important we
-capture the thought process that lead to a decision or design to avoid flip-flopping
+capture the thought process that leads to a decision or design to avoid flip-flopping
 needlessly.
 
 Hopefully we can make these proportional in effort to their magnitude — small changes