From 142c17fb03e5a667614c98dde4f12edc3f62e3fd Mon Sep 17 00:00:00 2001
From: latent-9 <296084221+latent-9@users.noreply.github.com>
Date: Mon, 3 Aug 2026 01:49:18 +1200
Subject: [PATCH] docs: fix wrong Request attribute for MAX_FORM_MEMORY_SIZE
 config

The MAX_FORM_MEMORY_SIZE entry cross-references
`.Request.max_form_memory_parts`, which does not exist. The per-request
attribute for this limit is `max_form_memory_size` (its default 500_000
matches this entry). The neighbouring entries follow the same convention
(MAX_CONTENT_LENGTH -> max_content_length, MAX_FORM_PARTS -> max_form_parts).
---
 docs/config.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/config.rst b/docs/config.rst
index 7138222d80..15ccbd6e78 100644
--- a/docs/config.rst
+++ b/docs/config.rst
@@ -343,7 +343,7 @@ The following configuration values are used internally by Flask:
     set to ``None``, no limit is enforced at the Flask application level.
 
     Each request defaults to this config. It can be set on a specific
-    :attr:`.Request.max_form_memory_parts` to apply the limit to that specific
+    :attr:`.Request.max_form_memory_size` to apply the limit to that specific
     view. This should be set appropriately based on an application's or view's
     specific needs.