chore: Updating docs

apps/next/.env.example

@@ -0,0 +1,6 @@
+# Since .env is gitignored, you can use .env.example to build a new `.env` file when you clone the repo.
+# Keep this file up-to-date when you add new variables to \`.env\`.
+# These examples are for development use only
+
+NEXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
+NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0

docs/getting-started/from-example.md

@@ -11,22 +11,21 @@ This example project is based on a **Next 14 application**. More example project
 Clone the repository using `gh` CLI and then install the project's dependencies.
 
 ```bash
-gh repo clone webscopeio/supabase-modules
+degit webscopeio/supabase-modules/examples/next my-app
 ```
 
 ```bash
 cd supabase-modules
+git init
 pnpm install
 ```
 
 ## 2. Set environment variables
 
-Create an `.env.local` file to store your environment variables.
+Create an `.env` file to store your environment variables. The environment variables below are safe to share and use for local development.
 
 <<< ../../.env.example
 
-The `.env.example` file above contains the environment variables that you can use for local development.
-
 To generate these environment variables you have to run Supabase locally first before development. Read more on [Your Supabase Instance](/getting-started/supabase).
 
 ## 3. Start your development server.