diff --git a/.changeset/khaki-experts-jump.md b/.changeset/khaki-experts-jump.md new file mode 100644 index 0000000000..a845151cc8 --- /dev/null +++ b/.changeset/khaki-experts-jump.md @@ -0,0 +1,2 @@ +--- +--- diff --git a/packages/context/src/lib/create-context.ts b/packages/context/src/lib/create-context.ts index 2e4ad4220f..0b4d3cde39 100644 --- a/packages/context/src/lib/create-context.ts +++ b/packages/context/src/lib/create-context.ts @@ -23,7 +23,7 @@ export type ContextType> = /** * Creates a typed Context. * - * Contexts are compared with with strict equality. + * Contexts are compared with strict equality. * * If you want two separate `createContext()` calls to referer to the same * context, then use a key that will by equal under strict equality like a diff --git a/packages/labs/cli/src/lib/commands/init.ts b/packages/labs/cli/src/lib/commands/init.ts index 8876c7e56b..7864fcf14e 100644 --- a/packages/labs/cli/src/lib/commands/init.ts +++ b/packages/labs/cli/src/lib/commands/init.ts @@ -48,7 +48,7 @@ export const makeInitCommand = (cli: LitCli): Command => { const name = options.name as string; /* * This is a basic check to ensure that the name is a valid custom - * element name. Will make sure you you start off with a character and + * element name. Will make sure you start off with a character and * at least one hyphen plus more characters. Will not check for the * following invalid use cases: * - starting with a digit diff --git a/packages/labs/eleventy-plugin-lit/README.md b/packages/labs/eleventy-plugin-lit/README.md index 369b7e6bfb..0e7a2714af 100644 --- a/packages/labs/eleventy-plugin-lit/README.md +++ b/packages/labs/eleventy-plugin-lit/README.md @@ -92,7 +92,7 @@ Use the `componentModules` setting to tell the plugin where to find the definitions of your components. Pass an array of paths to `.js` files containing Lit component definitions. -Paths are interpreted relative to to the directory from which the `eleventy` +Paths are interpreted relative to the directory from which the `eleventy` command is executed. Each `.js` file should be a JavaScript module (ESM) that imports `lit` with a diff --git a/packages/labs/preact-signals/README.md b/packages/labs/preact-signals/README.md index 6e5fca2e36..a5b541cb42 100644 --- a/packages/labs/preact-signals/README.md +++ b/packages/labs/preact-signals/README.md @@ -24,7 +24,7 @@ Preact Signals are a good place to start. It has integrations with other librari `SignalWatcher` is a mixin that makes an element watch all signal accesses during the element's reactive update lifecycle, then triggers an element update when signals change. This includes signals read in `shouldUpdate()`, `willUpdate()`, `update()`, `render()`, `updated()`, `firstUpdated()`, and reactive controller's `hostUpdate()` and `hostUpdated()`. -This effectively makes the the return result of `render()` a computed signal. +This effectively makes the return result of `render()` a computed signal. ```ts import {LitElement, html} from 'lit'; diff --git a/packages/labs/ssr/src/lib/render-value.ts b/packages/labs/ssr/src/lib/render-value.ts index 5b07d05ebb..7761dec1e0 100644 --- a/packages/labs/ssr/src/lib/render-value.ts +++ b/packages/labs/ssr/src/lib/render-value.ts @@ -269,7 +269,7 @@ const REGEXP_TEMPLATE_HAS_TOP_LEVEL_PAGE_TAG = * - Call `renderer.connectedCallback()` * - Emit `renderer.renderAttributes()` * - `text` - * - Emit end of of open tag `>` + * - Emit end of open tag `>` * - `custom-element-shadow` * - Emit `renderer.renderShadow()` (emits `