docs: noted incremental generation/revalidation quirks in examples

Just that revalidation will occur constantly in development when used
with incremental generation.

examples/core/state_generation/src/templates/revalidation_and_incremental_generation.rs

@@ -33,6 +33,8 @@ pub fn get_template<G: Html>() -> Template<G> {
         .should_revalidate_fn(should_revalidate)
         .build_state_fn(get_build_state)
         .build_paths_fn(get_build_paths)
+        // WARNING: this will revalidate on every reload in development, because incremental
+        // generation is recalculated on every request in development
         .incremental_generation()
 }
 

packages/perseus/src/template/core.rs

@@ -15,7 +15,7 @@ use crate::utils::AsyncFnReturn;
 #[cfg(not(target_arch = "wasm32"))]
 use crate::utils::ComputedDuration;
 use crate::utils::PerseusDuration; /* We do actually want this in both the engine and the
-                                     * browser */
+                                    * browser */
 use crate::Html;
 #[cfg(not(target_arch = "wasm32"))]
 use crate::Request;