From bb5b07be261e05de239af04d36d480639f5832ee Mon Sep 17 00:00:00 2001
From: Robert <49005401+Gitznik@users.noreply.github.com>
Date: Thu, 22 Sep 2022 16:59:37 +0200
Subject: [PATCH] Docs: Fix some typos in connection-checking.yml (#17028)

Fixes some formatting issues and hopefully makes the guide slightly easier to follow.
---
 .../tutorials/cdk-tutorial-python-http/connection-checking.md   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/connector-development/tutorials/cdk-tutorial-python-http/connection-checking.md b/docs/connector-development/tutorials/cdk-tutorial-python-http/connection-checking.md
index 16c90f1c6396e..427f519206ebc 100644
--- a/docs/connector-development/tutorials/cdk-tutorial-python-http/connection-checking.md
+++ b/docs/connector-development/tutorials/cdk-tutorial-python-http/connection-checking.md
@@ -4,7 +4,7 @@ The second operation in the Airbyte Protocol that we'll implement is the `check`
 
 This operation verifies that the input configuration supplied by the user can be used to connect to the underlying data source. Note that this user-supplied configuration has the values described in the `spec.yaml` filled in. In other words if the `spec.yaml` said that the source requires a `username` and `password` the config object might be `{ "username": "airbyte", "password": "password123" }`. You should then implement something that returns a json object reporting, given the credentials in the config, whether we were able to connect to the source.
 
-In order to make requests the API, we need to specify the access 
+In order to make requests to the API, we need to specify the access. 
 In our case, this is a fairly trivial check since the API requires no credentials. Instead, let's verify that the user-input `base` currency is a legitimate currency. In `source.py` we'll find the following autogenerated source:
 
 ```python