Update docs

docs/.vitepress/sidebar.en.ts

@@ -18,7 +18,7 @@ export default {
       items: [
         {text: 'Troubleshooting', link: '/en/guide/troubleshooting'},
         {text: 'Build on Windows', link: '/en/guide/build-on-windows'},
-        {text: 'Build with glibc (experimental)', link: '/en/guide/build-with-glibc'},
+        {text: 'Build with GNU libc', link: '/en/guide/build-with-glibc'},
       ],
     }
   ],

docs/.vitepress/sidebar.zh.ts

@@ -18,7 +18,7 @@ export default {
       items: [
         {text: '故障排除', link: '/zh/guide/troubleshooting'},
         {text: '在 Windows 上构建', link: '/zh/guide/build-on-windows'},
-        {text: '构建 glibc 兼容的二进制', link: '/zh/guide/build-with-glibc'},
+        {text: '构建 GNU libc 兼容的二进制', link: '/zh/guide/build-with-glibc'},
       ],
     }
   ],

docs/en/guide/build-with-glibc.md

@@ -13,8 +13,8 @@ However, there are some issues with pure static linking of musl-libc binaries on
 - The FFI extension in PHP cannot be used.
 - In some extreme cases, performance issues may occur. See [musl-libc performance issues](https://github.com/php/php-src/issues/13648).
 
-Different Linux distributions use different default libc. F
-or example, Alpine Linux uses musl libc, while most Linux distributions use glibc. 
+Different Linux distributions use different default libc. 
+For example, Alpine Linux uses musl libc, while most Linux distributions use glibc. 
 However, even so, we cannot directly use any distribution using glibc to build portable static binaries because glibc has some issues:
 
 - Binaries built with gcc and other tools on newer versions of distributions cannot run on older versions of distributions.