From 5c7475a6e89990cee45abfec8f396524bc122fa1 Mon Sep 17 00:00:00 2001
From: matamatanot <39780486+matamatanot@users.noreply.github.com>
Date: Wed, 24 Mar 2021 11:03:51 +0900
Subject: [PATCH] Fix typo in eslint doc (#23338)

## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.

## Documentation / Examples

- [ ] Make sure the linting passes
---
 docs/basic-features/eslint.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/basic-features/eslint.md b/docs/basic-features/eslint.md
index 019cc1d7c3..4eee6bb4bf 100644
--- a/docs/basic-features/eslint.md
+++ b/docs/basic-features/eslint.md
@@ -34,7 +34,7 @@ Here's an example of an `.eslintrc.json` file:
 ```
 
 - Extending the original base of rules (`plugin:@next/next/recommended`) is highly recommended to
-  catch and fix significant Next.js issues in your application
+  catch and fix significant Next.js issues in your application.
 - Including `@babel/eslint-parser` with the `next/babel` preset ensures that all language features
   supported by Next.js will also be supported by ESLint. Although `@babel/eslint-parser` can parse
   TypeScript, consider using
-- 
GitLab