docs: clarify file names and what each script creates

Author: booc0mtaco

.storybook/components/Docs/Guidelines/Theming.stories.mdx

@@ -4,18 +4,20 @@ import { Canvas, Meta } from '@storybook/blocks';
 
 # Theming overview
 
-"Theming", in the context of EDS, is the process of overriding the default styles of EDS components to match a different brand (or "theme"). The "Theming" directory in storybook demonstrates examples of theming:
+"Theming", in the context of EDS, is the process of overriding the default styles of EDS components to match a different brand (or "theme"). We include useful examples under "Pages":
 
 - A [wireframe theme](./?path=/story/pages-theming-wireframedemo--default) (an unbranded theme that can be used for prototyping a product before it has an official visual style).
 
+Below are instructions on how to use the tooling and tokens to define custom theme values for a project.
+
 ## How to apply a theme in another product
 
 EDS comes with some tooling to allow easy transfer of theme data from Figma (or some style-dictionary compatible format) into code.
 
 * `eds-init-theme` - This command sets up the initial file(s) for theming your application
 * `eds-apply-theme` - This command parses the style dictionary files to generate the tokens (CSS Variables) used by EDS
 
-Each of these tools reads config to figure out where to read/write files. This can be defined in several ways, e.g., a top-level file `eds.config.js`, or as a key-value set in package.json. Example:
+Each of these tools reads config to figure out where to read/write files. This can be defined in several ways, e.g., a top-level file `.edsrc.json`, or as a key-value set in package.json. Example:
 
 `package.json`
 
@@ -26,13 +28,22 @@ Each of these tools reads config to figure out where to read/write files. This c
 },
 ```
 
-`json` determines where the core theme file will be stored, and `css` determines where the resulting css token file will be stored.
+`.edsrc.json`
+
+```json
+{
+  "json": "src/components/",
+  "css": "src/components/"
+}
+```
+
+`json` determines where the core theme file will be copied to OR read from, and `css` determines where the resulting css token file will be stored.
 
 ### eds-init-theme
 
-EDS comes pre-packaged with token values that define the base style and character of the system. Users of EDS can theme certain aspects of all components, or details on specific components. This tool will set up your project to have its own theme overrides.
+This will create an initial JSON file `app-theme.json` that defines ALL the available tokens for EDS that you can edit. 
 
-This will create an initial JSON file that defines ALL the available tokens for EDS.
+EDS comes pre-packaged with many tokens that define the base style and character of the system. Users of EDS can theme certain aspects of all components, or details on specific components.
 
 ```json
 {
@@ -68,9 +79,9 @@ This will create an initial JSON file that defines ALL the available tokens for
 
 ### eds-apply-theme
 
-After initializing the theme file, make changes to the JSON to reflect what has been defined by design. When changes are made, you can generate the corresponding CSS values using `eds-apply-theme`.
+After making changes to the `app-theme.json` to reflect what has been defined by design, update the CSS token file by running `npx eds-apply-theme`.
 
-Once run, you will have a CSS file that includes a set of token values that can be used in the app as appropriate.
+Once run, you will have a CSS file `app-theme.css` that includes a set of token values that can be used in the app as appropriate.
 
 ```css
 /**
@@ -90,7 +101,9 @@ Once run, you will have a CSS file that includes a set of token values that can
 }
 ```
 
-Add this file to your core app root file. That's it! Now, your theme will be applied to the tokens used by EDS components. Further changes require re-running `eds-apply-theme`.
+Add this file to your core app root file. That's it! Now, the theme will be applied to the tokens used by EDS components. To make other changes, edit `app-theme.json`, then re-run `npx eds-apply-theme`.
+
+**NOTE**: do not edit this file directly. Instead, follow the instructions at the top of the file!
 
 ## How to manually apply a theme in another product