From 8548d44244b406ea3e7ff695127d04e25f7e042c Mon Sep 17 00:00:00 2001
From: imageck <101450105+imageck@users.noreply.github.com>
Date: Sat, 2 Sep 2023 14:23:33 +0500
Subject: [PATCH] Minor formatting fix in 02-static-site-generation.mdx

---
 .../02-rendering/02-static-site-generation.mdx                  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/03-pages/01-building-your-application/02-rendering/02-static-site-generation.mdx b/docs/03-pages/01-building-your-application/02-rendering/02-static-site-generation.mdx
index 70997d47fa4b..7de99342d14f 100644
--- a/docs/03-pages/01-building-your-application/02-rendering/02-static-site-generation.mdx
+++ b/docs/03-pages/01-building-your-application/02-rendering/02-static-site-generation.mdx
@@ -108,7 +108,7 @@ However, which `id` you want to pre-render at build time might depend on externa
 
 Later, you might add the second post with `id: 2`. Then you'd want to pre-render `posts/2` as well.
 
-So your page **paths** that are pre-rendered depend on external data**.** To handle this, Next.js lets you `export` an `async` function called `getStaticPaths` from a dynamic page (`pages/posts/[id].js` in this case). This function gets called at build time and lets you specify which paths you want to pre-render.
+So your page **paths** that are pre-rendered depend on external data. To handle this, Next.js lets you `export` an `async` function called `getStaticPaths` from a dynamic page (`pages/posts/[id].js` in this case). This function gets called at build time and lets you specify which paths you want to pre-render.
 
 ```jsx
 // This function gets called at build time