From 22a9899226b0dfefc40c5b3bebcc1db8522e9f02 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ma=C3=ABl=20Belval?=
 <58433201+mael-belval@users.noreply.github.com>
Date: Thu, 11 Jul 2024 14:48:54 +0200
Subject: [PATCH] doc: add missing bactick

Add a single backtick causing code rendering issue
---
 packages/docs/guide/essentials/route-matching-syntax.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/docs/guide/essentials/route-matching-syntax.md b/packages/docs/guide/essentials/route-matching-syntax.md
index 09c2515a0..23a531793 100644
--- a/packages/docs/guide/essentials/route-matching-syntax.md
+++ b/packages/docs/guide/essentials/route-matching-syntax.md
@@ -117,7 +117,7 @@ Note that `*` technically also marks a parameter as optional but `?` parameters
 If the route segment contains more than **just an optional parameter**, it won't match a path **without the trailing slash**. For example:
 
 - `/users/:uid?-:name?` won't match `/users`, only `/users/-` or even `/users/-/`
-- `/users/:uid(\\d+)?:name? won't match `/users`, only `/users/`, `/users/2`, `/users/2/`, etc
+- `/users/:uid(\\d+)?:name?` won't match `/users`, only `/users/`, `/users/2`, `/users/2/`, etc
 
 You can play around with the matching syntax [in the playground](https://paths.esm.dev/?p=AAMsIPQg4AoKzidgQFoEXAmw-IEBBRYYOE0SkABTASiz1qgBpgQA1QTsFjAb3h2onsmlAmGIFsCXjXh4AIA.&t=/users/2/#)