small updates

docs/content/2.guide/1.concepts/3.rendering.md

@@ -81,16 +81,15 @@ Nitro is the new [server engine](/guide/concepts/server-engine) that powers Nuxt
 
 > 🧪 Route rules are still under active development, and subject to change.
 
-Previously every page (or **route**) of a Nuxt application and server must use the same rendering mode, client-side or universal. But in various cases, some pages could be generated at build time, while others should be client-side rendered. For example, think of a content website with an admin section. Every content page should be primarily static and generated once, but the admin section requires registration and behaves more like a dynamic application.
+Previously every route/page of a Nuxt application and server must use the same rendering mode, client-side or universal. But in various cases, some pages could be generated at build time, while others should be client-side rendered. For example, think of a content website with an admin section. Every content page should be primarily static and generated once, but the admin section requires registration and behaves more like a dynamic application.
 
-Nuxt 3 starting from rc.12 comes with the public beta for route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route! Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [nitro caching layer](https://nitro.unjs.io/guide/introduction/cache). Whenever possible, route rules will be automatically applied to the deployment platform's native rules (currently netlify and vertical are supported).
-
-* `redirect` - Define server-side redirects.
-* `ssr` - Disables server-side rendering for sections of your app and make them SPA-only with `ssr: false`
-* `cors` - Automatically adds cors headers with `cors: true` - you can customize the output by overriding with `headers`
-* `headers` - Add specific headers to sections of your site - for example, your assets
-* `static` and `swr` - `static` enables a single (on-demand) build; `swr` enables a static build, that lasts for a configurable TTL. (currently enables full incremental static generation on netlify, with Vercel coming soon)
+Nuxt 3 starting from rc.12 comes with the public beta for route rules and hybrid rendering support. Using route rules you can define rules for a group of nuxt routes, change rendering mode or assign a cache strategy based on route! Nuxt server will automatically register corresponding middleware and wrap routes with cache handlers using [nitro caching layer](https://nitro.unjs.io/guide/introduction/cache). Whenever possible, route rules will be automatically applied to the deployment platform's native rules (currently Netlify and Vercel are supported).
 
+- `redirect` - Define server-side redirects.
+- `ssr` - Disables server-side rendering for sections of your app and make them SPA-only with `ssr: false`
+- `cors` - Automatically adds cors headers with `cors: true` - you can customize the output by overriding with `headers`
+- `headers` - Add specific headers to sections of your site - for example, your assets
+- `static` and `swr` - `static` enables a single (on-demand) build; `swr` enables a static build, that lasts for a configurable TTL. (currently enables full incremental static generation on Netlify, with Vercel coming soon)
 
 **Examples:**