From 7ea263ba6ffc208388e7fb1c2c68222643921871 Mon Sep 17 00:00:00 2001
From: Alvyn Berg <21360440+Alvynskio@users.noreply.github.com>
Date: Fri, 25 Jul 2025 12:23:29 -0400
Subject: [PATCH] fix: typo in faq.rst

Correct grammar. Original sentence was "That means it checker takes your specification and requirements, ..." and the corrected sentence is "That means a checker ...".
---
 docs/intro/faq.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/intro/faq.rst b/docs/intro/faq.rst
index 8e06680..3f38a5e 100644
--- a/docs/intro/faq.rst
+++ b/docs/intro/faq.rst
@@ -38,7 +38,7 @@ What does TLA stand for?
 How does TLA+ test specifications?
 ==================================
 
-There are a few different tools that work with TLA+, but the main one is called TLC, which does :term:`model checking`. That means it checker takes your specification and requirements, then checks *every possible behavior of the spec* against those requirements.
+There are a few different tools that work with TLA+, but the main one is called TLC, which does :term:`model checking`. That means a checker takes your specification and requirements, then checks *every possible behavior of the spec* against those requirements.
 
 This gives much more thorough coverage than something like unit tests. Consider a system where three processes each do four sequential steps in parallel. There are 34,650 possible interleavings and 415,800 possible distinct states. TLC will check every single one.