📝 Fix minor typos (#12516)

diff --git a/fastapi/param_functions.py b/fastapi/param_functions.py
index 7ddaace25a936dcb30a82dbf28e8a0d70b72e5df..b3621626cfd0264c3d82f9db02711bd17a23b994 100644 (file)
--- a/fastapi/param_functions.py
+++ b/fastapi/param_functions.py
@@ -2298,7 +2298,7 @@ def Security(  # noqa: N802
             dependency.
 
             The term "scope" comes from the OAuth2 specification, it seems to be
-            intentionaly vague and interpretable. It normally refers to permissions,
+            intentionally vague and interpretable. It normally refers to permissions,
             in cases to roles.
 
             These scopes are integrated with OpenAPI (and the API docs at `/docs`).

diff --git a/fastapi/security/oauth2.py b/fastapi/security/oauth2.py
index 9720cace0575e90242b772cb5d9556ffbe212141..6adc55bfeb150bd9421a551acf388532d8b7320b 100644 (file)
--- a/fastapi/security/oauth2.py
+++ b/fastapi/security/oauth2.py
@@ -52,7 +52,7 @@ class OAuth2PasswordRequestForm:
     ```
 
     Note that for OAuth2 the scope `items:read` is a single scope in an opaque string.
-    You could have custom internal logic to separate it by colon caracters (`:`) or
+    You could have custom internal logic to separate it by colon characters (`:`) or
     similar, and get the two parts `items` and `read`. Many applications do that to
     group and organize permissions, you could do it as well in your application, just
     know that that it is application specific, it's not part of the specification.
@@ -194,7 +194,7 @@ class OAuth2PasswordRequestFormStrict(OAuth2PasswordRequestForm):
     ```
 
     Note that for OAuth2 the scope `items:read` is a single scope in an opaque string.
-    You could have custom internal logic to separate it by colon caracters (`:`) or
+    You could have custom internal logic to separate it by colon characters (`:`) or
     similar, and get the two parts `items` and `read`. Many applications do that to
     group and organize permissions, you could do it as well in your application, just
     know that that it is application specific, it's not part of the specification.