From ec160751d7ecdfe9c58190921ad415fa5ea2f8ce Mon Sep 17 00:00:00 2001
From: Jeff Bowman <10966749+InteXX@users.noreply.github.com>
Date: Sat, 25 Mar 2023 10:04:16 -0800
Subject: [PATCH] Simple grammar tuneup

---
 docs/faq/per-request-scope.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/faq/per-request-scope.rst b/docs/faq/per-request-scope.rst
index 6c9045a..85377ed 100644
--- a/docs/faq/per-request-scope.rst
+++ b/docs/faq/per-request-scope.rst
@@ -2,7 +2,7 @@
 How do I work with per-request lifetime scope?
 ==============================================
 
-In applications that have a request/response semantic (e.g., :doc:`ASP.NET MVC <../integration/mvc>` or :doc:`Web API <../integration/webapi>`), you can register dependencies to be "instance-per-request," meaning you will get a one instance of the given dependency for each request handled by the application and that instance will be tied to the individual request lifecycle.
+In applications that have a request/response semantic (e.g., :doc:`ASP.NET MVC <../integration/mvc>` or :doc:`Web API <../integration/webapi>`), you can register dependencies to be "instance-per-request," meaning you will get one instance of the given dependency for each request handled by the application and that instance will be tied to the individual request lifecycle.
 
 In order to understand per-request lifetime, you should have a good understanding of :doc:`how dependency lifetime scopes work in general <../lifetime/instance-scope>`. Once you understand how dependency lifetime scopes work, per-request lifetime scope is easy.