Fix various typos in docc articles (#155)

### Motivation

A few typos in some doc articles.

### Modifications

Fixed the typos.

### Result

Fewer typos in docs.

### Test Plan

N/A

Author: gjcairo

Sources/swift-openapi-generator/Documentation.docc/Articles/API-stability-of-generated-code.md

@@ -10,7 +10,7 @@ This document outlines the API stability goals for the generated code to help yo
 
 ### Example changes
 
-There are three API bounderies to consider:
+There are three API boundaries to consider:
 - **HTTP**: the requests and responses sent over the network
 - **OpenAPI**: the description of the API using the OpenAPI specification
 - **Swift**: the client or server code generated from the OpenAPI document
@@ -60,7 +60,7 @@ Let's consider an example where you're creating a Swift library that provides a
 You can hide the generated client code as an implementation detail and provide a hand-written Swift API to your users using the following steps:
 
 1. Create a library target that is not exposed as a product, called, for example, `GeneratedGreetingClient`, which uses the Swift OpenAPI Generator package plugin.
-2. Create another library target that is exposed as a product, called, for example, `Greeter`, which imports the depends on the `GeneratedGreetingClient` target but doesn't use the imported types in its public API.
+2. Create another library target that is exposed as a product, called, for example, `Greeter`, which depends on the `GeneratedGreetingClient` target but doesn't use the imported types in its public API.
 
 This way, you are in full control of the public API of the `Greeter` library, but you also benefit from calling the service using generated code.
 

Sources/swift-openapi-generator/Documentation.docc/Articles/Contributing-to-Swift-OpenAPI-Generator.md

@@ -22,7 +22,7 @@ The code generator project is written in Swift and can be thought of as a functi
 
 The generated Swift code depends on the runtime library, so some features might require coordinated changes in both the runtime and generator repositories.
 
-Similarly, any changes to the transport and middleware protocols in the runtime library must consider the impact on existing existing transport and middleware implementation packages.
+Similarly, any changes to the transport and middleware protocols in the runtime library must consider the impact on existing transport and middleware implementation packages.
 
 > Tip: For non-trivial changes affecting the API, consider writing a proposal. For more, check out <doc:Proposals>.
 
@@ -44,7 +44,7 @@ To use this functionality, use an SPI import:
 
 ### Example contribution workflow
 
-Let's walk through the steps to implement a miising OpenAPI feature that requires changes in multiple repositories. For example, adding support for a [new query style][0].
+Let's walk through the steps to implement a missing OpenAPI feature that requires changes in multiple repositories. For example, adding support for a [new query style][0].
 
 1. Clone the generator and runtime repositories and set up a development environment where the generator uses the local runtime package dependency, by either:
 

Sources/swift-openapi-generator/Documentation.docc/Articles/Project-scope-and-goals.md

@@ -20,7 +20,7 @@ As a result, the generated code may not always be idiomatic Swift style or confo
 
 If you require the generated code to conform to specific style, we recommend you preprocess the OpenAPI document to update the identifiers to produce different code.
 
-For larger documents, you may want to do this programatically and, if you are doing so in Swift, you could use [OpenAPIKit][0], which is the same library used by Swift OpenAPI Generator.
+For larger documents, you may want to do this programmatically and, if you are doing so in Swift, you could use [OpenAPIKit][0], which is the same library used by Swift OpenAPI Generator.
 
 > Warning: Understand which identifiers can be changed without impacting the wire protocol for the API before attempting to preprocess the OpenAPI document.