(docs) fix grammar errors

Author: jcubic

docs/blog/2025-02-20-lexer.md

@@ -41,7 +41,7 @@ The limitation of syntax extension lead into introducing a new Lexer and a Strea
 Parser (if you're interested in this topic I will be writing an article about this in the
 future).
 
-The new Lexer is much simpler and easier to maintain, only had one bug recenly related to
+The new Lexer is much simpler and easier to maintain, only had one bug recently related to
 Lexer inner working ([#433](https://github.com/jcubic/lips/issues/433)).
 
 The new Lexer is a class that have rules for the state machine, this is an example
@@ -62,7 +62,7 @@ Lexer._rules = [
 ]
 ```
 
-The single rule is consisted of a currect character, next character, and a previous
+The single rule is consisted of a current character, next character, and a previous
 character (they can be single character strings or regular expressions).  If the character
 is null it can be any character. The last two elements of the array are the starting and
 the ending state (they are symbols so they are unique values).
@@ -82,7 +82,7 @@ That's why in above example there are no rule like this:
 
 This rule may be added in the future to speed up the Lexer.
 
-### Exmaple
+### Example
 
 When we have a string like this:
 
@@ -91,11 +91,11 @@ When we have a string like this:
 ```
 
 It matches the second rule because the first character is a quote, so it enters
-`Lexer.string` state.  The first rule don't match becuase the inital state is null. For
-characters `foo` it collects the tokens becasue no rule match them. When it finds slash
+`Lexer.string` state.  The first rule don't match because the initial state is null. For
+characters `foo` it collects the tokens because no rule match them. When it finds slash
 `\` it changes state from `Lexer.string` to `Lexer.string_escape`, and for next character
 it enters again `Lexer.string`.  Then it consumes sequence of characters `bar`, and the
-last quote maches the first rule. And that's how we have the full token.
+last quote matches the first rule. And that's how we have the full token.
 
 ### Syntax Extensions and Constants
 
@@ -118,6 +118,6 @@ maintain. If you want to look how it works for yourself. You can jump into
 search for `"class Lexer"`, `"Lexer._rule"`, `Object.defineProperty(Lexer, 'rules'`.
 
 The source code is in one file, so to navigate you need to use search. I've made an attempt to split
-the code into modules, but failed. Becuse of Rollup errors about circular dependencies.
+the code into modules, but failed. Because of Rollup errors about circular dependencies.
 
 This was first part of articles about [LIPS Scheme Internals](https://github.com/jcubic/lips/issues/437).