Confusion at 'A Review of Filters' Section in the Spring Security/Servlet Applications/ Architecture.

Expected Behavior
On the Spring Security/Servlet Applications/ Architecture docs page, there are 3 figures. In each figure, under the 'FilterChain' container, Filter0, Filter1, Filter2 and Servlet components are mentioned. And in the other figures, the deeper relationships of the filter chains are mentioned in the Filter1 component. When I was reading the docs for the first time to understand the architecture of Spring Security, I was pretty confused by Filter0 and Filter2, like what they are actually doing? What do they mean? Why are they shown here? Do they have any meaning?
The expected behaviour is that Filter0 should be replaced with appropriate wording, like 'SomeOtherFilters' or 'AppFilters'. By updating such wording, it will make it clear to the reader of the docs who wants to understand Spring Security.

Current Behaviour
Current Behaviour is visible on the Docs:
https://docs.spring.io/spring-security/reference/servlet/architecture.html

Having such clear wording will clear the confusion that Security Filters can exist at any level in the FilterChain components

Context

How has this affected me?

• When I read the docs, I was pretty confused about why DelegatingFilterProxy is not shown in the Component box, Filter0 and why Filter1? I was not able to grasp a clear picture of the flow.

How did I understand this?

• I took the link and pasted in the Antigravity AI tool, and stated that I am having confusion understanding the docs of the architecture, and then it stated clearly those thinking and understanding gaps.

Start at the Servlet Applications Architecture page linked in the issue and inspect the three figures, especially the FilterChain labels and the Filter1 relationships. Determine how Filter0 and Filter2 are intended to represent filters, then update the diagram wording so the roles are clear to first-time readers. Done means the figures no longer leave the purpose of those placeholder labels ambiguous.