feat(docs): A few minor tweaks on the email dev section

Author: gabrielmfern

apps/docs/cli.mdx

@@ -8,7 +8,8 @@ icon: 'square-terminal'
 
 ## `email dev`
 
-Starts a local development server that will watch your files and automatically rebuild your email when you make changes.
+Starts a local development server that will watch your files and automatically rebuild 
+your email template when you make changes.
 
 ### Where can I place my static files for previewing?
 
@@ -22,7 +23,7 @@ This does adjust to your `--dir` option, so if your `emails` directory was insid
 `./src/emails`, you would place your static files inside `./src/emails/static`.
 
 These static files are directly served from our preview server by looking into the
-requests made into that end with `/static` (i.e. `http://localhost:3000/static/...`) and serving the files at that point,
+requests made into it that end with `/static` (i.e. `http://localhost:3000/static/...`) and serving the files at that point,
 this also allows for you to have images inside your emails like so:
 
 ```jsx
@@ -38,12 +39,11 @@ export default Email(props) {
 <Info>
   This does not mean your images are hosted for you to send the emails.
 
-  If you do send the rendered email, and you are trying to link to an image 
-  or something similar inside `emails/static`, they will not load properly on the email.
-</Info>
+  If you do send the rendered email, and you are trying to link to an image, 
+  or some other asset inside `emails/static`, they will not load on the email that was sent.
 
-Of curse, more often than not you will need to host your images on a CDN, so we recommend
-you change the `src` to the CDN's base URL based on the environment like:
+  We recommend that you use a different source link to your files depending on whether you're
+  running in production or not. Here's an example
 
 ```jsx
 const baseURL = process.env.NODE_ENV === 'production' 
@@ -58,15 +58,16 @@ export default Email(props) {
   )
 }
 ```
-
-You can refer to our [demo emails source code](https://demo.react.email/preview/vercel-invite-user.tsx?view=source) for an example of how we do this.
+  You can refer to our [demo emails source code](https://demo.react.email/preview/vercel-invite-user.tsx?view=source) 
+  for an example of how we do this with our demo deploy on Vercel.
+</Info>
 
 ### How can I define props specific to the email's preview?
 
 Considering that you are already default exporting the React component
 that will render as your email template, you can just define a `PreviewProps` with it as follows:
 
-```jsx
+```jsx Email template
 export default Email(props) {
   return (
     <div>
@@ -81,14 +82,21 @@ Email.PreviewProps = {
 ```
 
 And then when opening this email's preview the `PreviewProps` 
-will be used as props into Email.
+will be used as props into Email. So, in a nutshell, it will render the same as if you were to do:
+
+```jsx Another file
+import Email from './path-to-my-email';
+
+<Email {...Email.PreviewProps} />
+```
 
 ### How to make the preview server ignore directories?
 
 Once the preview server has started and is now open on `localhost`, the preview server
 reads recursively down into all of your files and directories. This can be disabled
-from a directory down by prefixing it with `_`, e.g. `components -> _components`. So if you wanted
-to make components for your emails, you could make a structure as follows:
+from a directory down by prefixing it with `_`, e.g. `components -> _components`. 
+
+So if you wanted to make components for your emails, you could have a file structure as follows:
 
 ```bash
 my-project
@@ -101,13 +109,15 @@ my-project
 └── tsconfig.json
 ```
 
+Then the only file that will be shown on the preview server is going to be your `email.tsx`.
+
 ### The heuristics for files to be considered emails
 
 To avoid uncanny files appearing in the sidebar of the preview server,
 we account for two heuristics to determine weather or not we should
 include it:
 
-1. If file has `.js, .jsx or .tsx` file extensions
+1. If a file has `.js, .jsx or .tsx` as their file extension
 2. If the file contains a `export default` expression by matching with the regex<br/>
 `/\bexport\s*default\b/gm`