From 2badc55ee59640f6ef1d25b2241db8b7dc8ecfb3 Mon Sep 17 00:00:00 2001
From: ChengQing <73209378+chengqing97@users.noreply.github.com>
Date: Fri, 10 Dec 2021 01:01:06 +0800
Subject: [PATCH] Update 05-chapter-4-testing-your-api.mdx

Fix typo.
---
 .../03-tutorial/05-chapter-4-testing-your-api.mdx               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/content/010-getting-started/03-tutorial/05-chapter-4-testing-your-api.mdx b/docs/content/010-getting-started/03-tutorial/05-chapter-4-testing-your-api.mdx
index cb3556bc..c7ac4eb5 100644
--- a/docs/content/010-getting-started/03-tutorial/05-chapter-4-testing-your-api.mdx
+++ b/docs/content/010-getting-started/03-tutorial/05-chapter-4-testing-your-api.mdx
@@ -88,7 +88,7 @@ mkdir tests && touch tests/Post.test.ts
 
 To ease testing, we'll create a small utility that we'll call `createTestContext`, which is designed for running integration tests.
 
-When run, it will boot your app in the same process as the test suite and expose an interface for your tests to interact with it. Jest runs each test suite in its own process, so if you have have say eight test suites running in parallel that means you'll have eight app processes running too.
+When run, it will boot your app in the same process as the test suite and expose an interface for your tests to interact with it. Jest runs each test suite in its own process, so if you have say eight test suites running in parallel that means you'll have eight app processes running too.
 
 Create a `tests/__helpers.ts` module with the following contents.