From 2601f5598264472a8392948509f3e13301f19ee9 Mon Sep 17 00:00:00 2001
From: vinay <94120295+vinaykulk621@users.noreply.github.com>
Date: Sun, 2 Apr 2023 10:53:15 +0530
Subject: [PATCH] (Fix)(Tests)Fix typo in unit testing (#47644)

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation or adding/fixing Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md



## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->
Fix Typo In Unit Testing
---
 test/unit/accept-headers.test.ts | 2 +-
 test/unit/mitt.test.ts           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/test/unit/accept-headers.test.ts b/test/unit/accept-headers.test.ts
index 4b95f3de48..ca789bfa92 100644
--- a/test/unit/accept-headers.test.ts
+++ b/test/unit/accept-headers.test.ts
@@ -11,7 +11,7 @@ describe('acceptLanguage', () => {
     expect(language).toEqual('en-gb')
   })
 
-  it('returns empty string with header is empty', () => {
+  it('returns an empty string with header is empty', () => {
     const language = acceptLanguage('')
     expect(language).toEqual('')
   })
diff --git a/test/unit/mitt.test.ts b/test/unit/mitt.test.ts
index 541f3dc49f..964af97bcc 100644
--- a/test/unit/mitt.test.ts
+++ b/test/unit/mitt.test.ts
@@ -3,7 +3,7 @@ import mitt from 'next/dist/shared/lib/mitt'
 
 describe('mitt', () => {
   describe('With listeners', () => {
-    it('should listen to a event', () => {
+    it('should listen to an event', () => {
       return new Promise((resolve) => {
         const ev = mitt()
         ev.on('sample', resolve)