rewording and style fixes

Author: kaumnen

src/content/docs/workers/tutorials/automated-analytics-reporting/index.mdx

@@ -36,7 +36,7 @@ Before you start, make sure you:
 4. [Enable Email Routing](/email-routing/get-started/enable-email-routing/) for your domain.
 5. Create Cloudflare's [Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/).
 
-## Create a Worker
+## 1. Create a Worker
 
 While you can create a Worker using the Cloudflare dashboard, creating a Worker using the `c3` CLI is recommended as it provides a more streamlined development experience and allows you to test your Worker locally.
 
@@ -48,7 +48,7 @@ First, use the `c3` CLI to create a new Cloudflare Workers project.
 	args={"account-analytics"}
 />
 
-In this tutorial, we will name our Worker `account-analytics`.
+In this tutorial, name your Worker as `account-analytics`.
 
 <Render
 	file="c3-post-run-steps"
@@ -60,13 +60,13 @@ In this tutorial, we will name our Worker `account-analytics`.
 	}}
 />
 
-Now, the Worker is set up. Move into that project directory.
+Now, the Worker is set up. Move into your project directory:
 
 ```sh
 cd account-analytics
 ```
 
-Before we continue with the tutorial, let's install [`mimetext`](https://www.npmjs.com/package/mimetext) package.
+To continue with this tutorial, install the [`mimetext`](https://www.npmjs.com/package/mimetext) package:
 
 <Tabs> <TabItem label="pnpm">
 
@@ -88,7 +88,7 @@ yarn add mimetext
 
 </TabItem> </Tabs>
 
-## Update wrangler.toml
+## 2. Update wrangler.toml file
 
 [`wrangler.toml`](https://developers.cloudflare.com/workers/wrangler/configuration/) is the configuration file for your Worker. It was created when you ran `c3` CLI. Open `wrangler.toml` in your code editor and update it with the following configuration:
 
@@ -129,22 +129,20 @@ EMAIL_SUBJECT = "Cloudflare Analytics Report"
 
 Before you continue, update the following:
 
-1. `compatibility_date` with the current date.
-2. `destination_address` with the email address where you want to receive the analytics report.
-3. `[VARS]` with the environment variable values you want to use in your Worker.
+1. `compatibility_date`: Enter the current date.
+2. `destination_address`: Enter the email address where you want to receive the analytics report.
+3. `[VARS]`: Enter the environment variable values you want to use in your Worker.
 
 :::note[IMPORTANT]
 `destination_address` and `RECIPIENT_EMAIL` **must** contain [Email Routing verified email](/email-routing/get-started/enable-email-routing/) address.
 
-`SENDER_EMAIL` **must** be address on a domain that:
+`SENDER_EMAIL` **must** be an email address on a domain that is added to your Cloudflare domain and has Email Routing enabled.
 
-1. Is added to your Cloudflare domain
-2. Has Email Routing enabled.
-   :::
+:::
 
-## Update the Worker code
+## 3. Update the Worker code
 
-You will now add the code step by step to the `src/index.js` file. We will explain each part of the code as we go along.
+You will now add the code step by step to the `src/index.js` file. This tutorial will explain each part of the code.
 
 ### Add the required modules and Handlers
 
@@ -193,7 +191,7 @@ export default {
 };
 ```
 
-In the code above, we have defined two [Worker Handlers](/workers/runtime-apis/handlers/):
+The code above defines two [Worker Handlers](/workers/runtime-apis/handlers/):
 
 - `fetch`: This Handler executes when the Worker is accessed via HTTP. It fetches the analytics data, formats it and returns it as a response.
 - `scheduled`: This Handler executes at the scheduled time. It fetches the analytics data, formats it and sends an email with the analytics data.
@@ -271,7 +269,7 @@ async function fetchAnalytics(env) {
 }
 ```
 
-In the code above, we have defined a function `fetchAnalytics` that fetches analytics data from Cloudflare's GraphQL Analytics API. The function calculates yesterday's date, formats it for display, and sends a GraphQL query to the Analytics API to fetch the analytics data.
+In the code above, the `fetchAnalytics` function fetches analytics data from Cloudflare's GraphQL Analytics API. The `fetchAnalytics` function calculates yesterday's date, formats the date for display, and sends a GraphQL query to the Analytics API to fetch the analytics data.
 
 :::note
 `env.CF_API_TOKEN` and `env.CF_ACCOUNT_ID` are [Worker Secrets](/workers/configuration/secrets/). These variables are used to authenticate the request and fetch the analytics data for the specified account. You will add these secrets to your Worker after the code is complete.
@@ -281,12 +279,12 @@ This function returns the **raw** data for the previous day, including:
 
 - Traffic overview data (Total requests, Page views and Blocked threats)
 - Bandwidth data (Total bandwidth, Encrypted bandwidth and Cached bandwidth)
-- Caching & Encryption data (Encrypted requests, Cached requests, Encryption rate and Cache rate)
+- Caching and Encryption data (Encrypted requests, Cached requests, Encryption rate and Cache rate)
 - Browser data (Page views by browser)
 - HTTP status code data (Requests by status code)
 - HTTP version data (Requests by HTTP version)
 
-This data will be used to generate the analytics report. Let's add the function that formats this data.
+This data will be used to generate the analytics report. In the following step, you will add the function that formats this data.
 
 ### Add the data formatting function
 
@@ -410,16 +408,16 @@ This function sends an email with the formatted analytics data to the specified
 `sendEmail` function uses multiple environment variables that are set in the `wrangler.toml` file.
 :::
 
-## Test the Worker
+## 4. Test the Worker
 
 Now that you have updated the Worker code, you can test it locally using the `wrangler dev` command. This command starts a local server that runs your Worker code.
 
 Before you run the Worker, you need to add two Worker secrets:
 
 - `CF_API_TOKEN`: Cloudflare GraphQL Analytics API token you created earlier.
-- `CF_ACCOUNT_ID`: Your Cloudflare account ID. Can be found in the Cloudflare dashboard under the Workers & Pages Overview tab.
+- `CF_ACCOUNT_ID`: Your Cloudflare account ID. You can find your account ID in the Cloudflare dashboard under the **Workers & Pages** Overview tab.
 
-Let's create `.dev.vars` file in the root of your project directory and add the following:
+Create a `.dev.vars` file in the root of your project directory and add the following:
 
 ```sh
 CF_API_TOKEN=YOUR_CLOUDFLARE_API_TOKEN
@@ -432,35 +430,35 @@ Now, run the Worker locally:
 npx wrangler dev --remote
 ```
 
-Open your browser and visit `http://localhost:8787`. You should see the analytics data displayed in your browser.
+Open the `http://localhost:8787` URL on your browser. The browser will display analytics data.
 
-## Deploy the Worker and Worker secrets
+## 5. Deploy the Worker and Worker secrets
 
-Once you have tested the Worker locally, you can deploy it to Cloudflare's edge network:
+Once you have tested the Worker locally, you can deploy your Worker to Cloudflare's edge network:
 
 ```sh
 npx wrangler deploy
 ```
 
-CLI command will output the URL where your Worker is deployed. Before you can visit this URL in your browser to view the analytics data, you need to add two Worker secrets you already have locally to your deployed Worker:
+CLI command will output the URL where your Worker is deployed. Before you can use this URL in your browser to view the analytics data, you need to add two Worker secrets you already have locally to your deployed Worker:
 
 ```sh
 npx wrangler secret put <secret>
 ```
 
 Replace `<secret>` with the name of the secret you want to add. Repeat this command for `CF_API_TOKEN` and `CF_ACCOUNT_ID` secrets.
 
-Once you put the secrets, visit the `account-analytics.<YOUR_SUBDOMAIN>.workers.dev` to view the analytics data. You will also receive an email report to the specified recipient email address every day at 10:00 AM.
+Once you put the secrets, preview your analytics data at `account-analytics.<YOUR_SUBDOMAIN>.workers.dev`. You will also receive an email report to the specified recipient email address every day at 10:00 AM.
 
 If you want to disable a public URL for your Worker, you can do so by following these steps:
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
 
-2. In Account Home, select **Workers & Pages**, and then select `account-analytics` Worker.
+2. In Account Home, select **Workers & Pages**, then select `account-analytics` Worker.
 
-3. Go to **Settings** - **Domains & Routes**
+3. Go to **Settings** > **Domains & Routes**.
 
-4. Click 'Disable' to disable the public `account-analytics.<YOUR_SUBDOMAIN>.workers.dev` URL.
+4. Select **Disable** to disable the public `account-analytics.<YOUR_SUBDOMAIN>.workers.dev` URL.
 
 You have successfully created, tested and deployed a Worker that fetches analytics data from Cloudflare's GraphQL Analytics API and sends an email report via Email Routing.