[docs] be more specific about the definition of page endpoints (#5198)

* [docs] be more specific about the definition of page endpoints

* hopefully disambiguate by putting it after filename

* split

* apply suggestion

* Update documentation/docs/02-routing.md

Co-authored-by: Ben McCann <[email protected]>

* Update documentation/docs/02-routing.md

Co-authored-by: Ben McCann <[email protected]>

Co-authored-by: Ben McCann <[email protected]>

Author: gtm-nayan

documentation/docs/02-routing.md

@@ -100,7 +100,7 @@ The job of a [request handler](/docs/types#sveltejs-kit-requesthandler) is to re
 
 #### Page endpoints
 
-If an endpoint has the same filename as a page (except for the extension), the page gets its props from the endpoint — via `fetch` during client-side navigation, or via direct function call during SSR.
+If an endpoint has the same filename as a page (except for the extension), the page gets its props from the endpoint — via `fetch` during client-side navigation, or via direct function call during SSR. If a page uses syntax for [named layouts](/docs/layouts#named-layouts) or [matchers](/docs/routing#advanced-routing-matching) in its filename then the corresponding page endpoint's filename must also include them.
 
 A page like `src/routes/items/[id].svelte` could get its props from the `body` in the endpoint above: