From 88a65bb374e87a18816a780dbd4ae69d307aa85c Mon Sep 17 00:00:00 2001 From: Hynek Schlawack Date: Tue, 14 Oct 2025 22:26:26 +0200 Subject: [PATCH] Docs typo/markup fixes (#5829) --- docs/appcontext.rst | 4 ++-- docs/design.rst | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/appcontext.rst b/docs/appcontext.rst index f05468f5..81b73b47 100644 --- a/docs/appcontext.rst +++ b/docs/appcontext.rst @@ -141,8 +141,8 @@ real object, rather than the proxy. Use the my_signal.send(app) -Lifcycle of the Context ------------------------ +Lifecycle of the Context +------------------------ Flask dispatches a request in multiple stages which can affect the request, response, and how errors are handled. See :doc:`/lifecycle` for a list of all diff --git a/docs/design.rst b/docs/design.rst index 063f55ad..d8776a90 100644 --- a/docs/design.rst +++ b/docs/design.rst @@ -178,10 +178,10 @@ etc. Context locals are specific to the worker handling the activity, such as a thread, process, coroutine, or greenlet. The context and proxies help solve two development issues: circular imports, and -passing around global data. :data:`.current_app: can be used to access the +passing around global data. :data:`.current_app` can be used to access the application object without needing to import the app object directly, avoiding -circular import issues. :data:`.request`, :data:`.session`, and :data`.g` can be -imported to access the current data for the request, rather than needing to +circular import issues. :data:`.request`, :data:`.session`, and :data:`.g` can +be imported to access the current data for the request, rather than needing to pass them as arguments through every single function in your project.