fix(deps): update dependency next-sanity to v3 (#100)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Cody Olsen <81981+stipsan@users.noreply.github.com>

.env.local.example

@@ -1,9 +1,22 @@
+# Defaults, used by ./intro-template and can be deleted if the component is removed
 NEXT_PUBLIC_VERCEL_GIT_REPO_OWNER="sanity-io"
 NEXT_PUBLIC_VERCEL_GIT_PROVIDER="github"
 NEXT_PUBLIC_VERCEL_GIT_REPO_SLUG="nextjs-blog-cms-sanity-v3"
 
+# Required, find them on https://manage.sanity.io
 NEXT_PUBLIC_SANITY_PROJECT_ID=
 NEXT_PUBLIC_SANITY_DATASET=
 SANITY_API_READ_TOKEN=
+# Optional, useful if you plan to add API functions that can write to your dataset your dataset
+SANITY_API_WRITE_TOKEN=
+
+# Optional, can be used to change the Studio title in the navbar and differentiate between production and staging environments for your editors
+NEXT_PUBLIC_SANITY_PROJECT_TITLE="Next.js Blog with Sanity.io"
+
+# Optional, check the comments in pages/api/revalidate.ts for instructions on how to set it up
 SANITY_REVALIDATE_SECRET=
+
+# If `/api/preview?slug` URLs don't have a `secret` search parameter then static rendering will still be optimistically enabled but without
+# a `token` set. Instead, it'll check if the user have a valid Sanity session and have access to the project and dataset before any draft content is queried.
+# You can turn this off by setting this env var to "true" and only valid secrets will be allowed to bypass static rendering and harden the security.
 SANITY_REQUIRE_PREVIEW_SECRET=