docs: update pages automatic static optimization rendering page (#72545)

## Improving Documentation
I just add **Good to know** to below path note which was in a block but
not add the tag.
> Pages > Rendering > Automatic Static Optimization

**Before:**
> Statically generated pages are still reactive: Next.js will hydrate
your application client-side to give it full interactivity.

**Now:**
> **Good to know:** Statically generated pages are still reactive.
Next.js will hydrate your application client-side to give it full
interactivity.

Co-authored-by: Sam Ko <sam@vercel.com>

docs/02-pages/02-building-your-application/02-rendering/04-automatic-static-optimization.mdx

@@ -7,7 +7,7 @@ Next.js automatically determines that a page is static (can be prerendered) if i
 
 This feature allows Next.js to emit hybrid applications that contain **both server-rendered and statically generated pages**.
 
-> Statically generated pages are still reactive: Next.js will hydrate your application client-side to give it full interactivity.
+> **Good to know**: Statically generated pages are still reactive. Next.js will hydrate your application client-side to give it full interactivity.
 
 One of the main benefits of this feature is that optimized pages require no server-side computation, and can be instantly streamed to the end-user from multiple CDN locations. The result is an _ultra fast_ loading experience for your users.