chore: fix some typos in comments (#6317)

Signed-off-by: TechVest <techdashen@qq.com>
scrapy · Apr 17, 2024 · 5f67c01 · 5f67c01
1 parent 1d11ea3
commit 5f67c01
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/.git-blame-ignore-revs b/.git-blame-ignore-revs
@@ -1,7 +1,7 @@
 # .git-blame-ignore-revs
 # adding black formatter to all the code
 e211ec0aa26ecae0da8ae55d064ea60e1efe4d0d
-# re applying black to the code with default line length
+# reapplying black to the code with default line length
 303f0a70fcf8067adf0a909c2096a5009162383a
-# reaplying black again and removing line length on pre-commit black config
+# reapplying black again and removing line length on pre-commit black config
 c5cdd0d30ceb68ccba04af0e71d1b8e6678e2962
diff --git a/docs/topics/broad-crawls.rst b/docs/topics/broad-crawls.rst
@@ -116,7 +116,7 @@ Reduce log level
 When doing broad crawls you are often only interested in the crawl rates you
 get and any errors found. These stats are reported by Scrapy when using the
 ``INFO`` log level. In order to save CPU (and log storage requirements) you
-should not use ``DEBUG`` log level when preforming large broad crawls in
+should not use ``DEBUG`` log level when performing large broad crawls in
 production. Using ``DEBUG`` level when developing your (broad) crawler may be
 fine though.