chore(readme): perform copy edits (#19)

copy edits to the readme to improve readability, fix grammatical (and
naming) errors, etc.

README.md

@@ -1,4 +1,4 @@
-# Stencil Web-Types Output Target
+# Stencil Web Types Output Target
 
 <p align="center">
   <a href="https://www.npmjs.com/package/@stencil-community/web-types-output-target">
@@ -17,34 +17,35 @@
   </a>
 </p>
 
-A Stencil output target for generating [web-types](https://plugins.jetbrains.com/docs/intellij/websymbols-web-types.html#file-structure) to provide intellisense for Stencil components for HTML files.
+A Stencil output target for generating [web types](https://plugins.jetbrains.com/docs/intellij/websymbols-web-types.html#file-structure) to provide intellisense for Stencil components in HTML files.
 
 > [!NOTE]
-> This package is experimental - It's pre-v1.0, things may change over time.
+> This package follows [semantic versioning](https://semver.org).
+> Small breaking changes to the API may occur prior to hitting v1.0.
 
 ## Overview
 
-One of the core features of web components is the ability to create [custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements), which allow developers to reuse custom functionality defined in their components.
+One of the core features of web components is the ability to create [custom elements](https://developer.mozilla.org/en-US/docs/Web/Web_Components/Using_custom_elements), which allow developers to reuse custom functionality defined by their components.
 When Stencil compiles a project, it generates a custom element for each component in the project.
-Each of these [custom elements has an associated `tag` name](../components/component.md#component-options) that allows the custom element to be used in HTML files.
 
-By default, integrated development environments (IDEs) like JetBrains' WebStorm are not aware of a project's custom elements when authoring HTML.
-In order to enable more intelligent features in JetBrains products such as auto-completion, hover tooltips, etc., developers need to inform it of their project's custom elements.
+By default, integrated development environments (IDEs) like JetBrains' WebStorm are not aware of a project's custom elements.
+This causes the IDE to often warn developers that it doesn't have any information about their custom elements, and results in a poorer developement experience.
+In order to enable more intelligent features in JetBrains products, such as auto-completion, hover tooltips, etc., developers need to inform it of their project's custom elements.
 
-The `docs-web-types` output target tells Stencil to generate a JSON file containing this information.
+The `webTypesOutputTarget` output target tells Stencil to generate a JSON file containing this information.
 
-This is an opt-in feature and will save a JSON file containing web-types in a directory specified by the output target.
-Once the feature is enabled and your IDE is informed of the JSON file's location, HTML files can gain code editing features similar to TSX files.
+This is an opt-in feature and will write a JSON file containing web types in a directory specified by the output target.
+Once the feature is enabled and your IDE is informed of the JSON file's location, writing code in HTML files will have similar intellisense to that of TSX files.
 
 ## Set Up
 
-The web-types output target is not built in to Stencil itself.
-Instead, it's a third party package, that needs to be installed as a dev dependency:
+The output target is not built in to Stencil itself.
+It's a third party package, that needs to be installed as a dev-dependency:
 ```bash
 $ npm i --save-dev @stencil-community/web-types-output-target
 ```
 
-To generate custom element information for JetBrains IDE's, add the `docs-web-types` output target to your `stencil.config.ts`:
+To generate custom element information for JetBrains IDE's, add the `webTypesOutputTarget` output target to your `stencil.config.ts`:
 ```tsx
 import { Config } from '@stencil/core';
 import { webTypesOutputTarget } from '@stencil-community/web-types-output-target';
@@ -56,12 +57,12 @@ export const config: Config = {
 };
 ```
 
-To generate the JSON file, have Stencil build your project.
-Stencil will write a `web-types.json` to your project's root directory.
+Stencil will write a `web-types.json` to your project's root directory the next time the Stencil [build task](https://stenciljs.com/docs/cli#stencil-build) is run.
 
 ## Usage
 
-Web Types for your project can be picked by JetBrains IDEs by setting the `web-types` property in your project's `package.json` file:
+Once web types have been written to disk, they need to be picked up by the IDE.
+Web types for your project can be picked by JetBrains IDEs by setting the `web-types` property at the root level of your project's `package.json` file:
 
 ```json
 {
@@ -73,7 +74,7 @@ Web Types for your project can be picked by JetBrains IDEs by setting the `web-t
 ```
 
 Having this file locally on disk will allow your JetBrains IDE to pick up additional typings automatically.
-To provide these IDE-specific typings to users of your library, be sure to include the generated web-types file in your package's distributable by adding it to your `package.json#files` array.
+To provide these IDE-specific typings to users of your library, be sure to include the generated web types file in your package's distributable by adding it to your `package.json#files` array.
 
 ## References