fix: identify the typo error and corrected

README.md

@@ -176,7 +176,7 @@ Customers have the option to deploy this solution with PostgreSQL or Cosmos DB.
 
 
 To review PostgreSQL configuration overview and steps, follow the link [here](docs/postgreSQL.md).
-![Solution Architecture - Chat with your data PostgreSQL](/docs/images/architrecture_pg.png)
+![Solution Architecture - Chat with your data PostgreSQL](/docs/images/architecture_pg.png)
 
 To review Cosmos DB configuration overview and steps, follow the link [here](docs/employee_assistance.md).
 ![Solution Architecture - Chat with your data CosmosDB](/docs/images/architecture_cdb.png)

code/tests/functional/resources/README.md

@@ -1,7 +1,7 @@
 # Why is this here?
 
 The file [9b5ad71b2ce5302211f9c61530b329a4922fc6a4](9b5ad71b2ce5302211f9c61530b329a4922fc6a4) is required to stop the 
-tiktoken library from making a call out to the internet to retrive the required encoder.
+tiktoken library from making a call out to the internet to retrieve the required encoder.
 
 You can see where this happens in the code here https://github.com/openai/tiktoken/blob/1b9faf2779855124f05174adf1383e53689ed94b/tiktoken/load.py#L25,
 which calls out to https://openaipublic.blob.core.windows.net/encodings/cl100k_base.tiktoken.

docs/RELEASE_GUIDELINES.md

@@ -12,7 +12,7 @@ This repository uses GitHub's in-built [Releases](https://docs.github.com/en/rep
 
 # Automated releases
 
-In order to automate the generation of a changelog, the creation of a release, and the bumping of a version number, we use the [Conventional Changelog Action](https://github.com/TriPSs/conventional-changelog-action).
+In order to automate the generation of a change log, the creation of a release, and the bumping of a version number, we use the [Conventional Changelog Action](https://github.com/TriPSs/conventional-changelog-action).
 
 It works by inferring from the commit history what changes have been made, and hence what version should be assigned. This is why it is important for Pull Request titles to adhere to the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification, which many repositories use. This convention uses types such as `docs`, `fix`, `feat`, etc to label commits and PRs.
 

docs/design/adrs/2024-05-02-enable-project-versioning.md

@@ -1,4 +1,4 @@
-# Use Github Releases to manage project versioning
+# Use GitHub Releases to manage project versioning
 
 * **Status:** approved
 * **Proposer:** @frtibble