From 4e0f180fe3425b92d2c7b7e362182d17c21ee50b Mon Sep 17 00:00:00 2001 From: RW Date: Thu, 8 Feb 2024 08:18:26 +0100 Subject: [PATCH] Update routing.md --- docs/guide/routing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guide/routing.md b/docs/guide/routing.md index b6534532b0..2a1067ae6f 100644 --- a/docs/guide/routing.md +++ b/docs/guide/routing.md @@ -145,7 +145,7 @@ We have adapted the routing strongly to the express routing, but currently witho Route constraints execute when a match has occurred to the incoming URL and the URL path is tokenized into route values by parameters. The feature was intorduced in `v2.37.0` and inspired by [.NET Core](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-6.0#route-constraints). :::caution -Constraints aren't validation for parameters. If constraint aren't valid for parameter value, Fiber returns **404 handler**. +Constraints aren't validation for parameters. If constraints aren't valid for a parameter value, Fiber returns **404 handler**. ::: | Constraint | Example | Example matches |