@fusion.dev/helix 0.104.1 → 0.106.0

package/dist/table/root/table-root.d.ts

@@ -1,12 +1,11 @@
 import { HelixHeadlessTable } from '@fusion.dev/helix-headless/table';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary Tabular data laid out on a grid.
+ * @summary A table of data, laid out on a grid.
  *
  * @description
- * Hairline rules between rows and no fill, per the rule that depth comes from a
- * single border rather than from elevation. A dense table earns its density by
- * decorating none of it.
+ * Rows have hairline rules between them and no fill. Helix shows depth with a
+ * single border and no elevation, and a dense table adds no other decoration.
  *
  * @since 0.1.0
  * @status stable
@@ -15,10 +14,10 @@ import type { CSSResultGroup } from 'lit';
  *
  * @slot - The table's rows.
  *
- * @csspart live - The empty and loading lines again, in a region a screen reader hears when they change. Visually hidden in the styled tier.
+ * @csspart live - A live region that repeats the empty and loading text, so screen readers announce it when it changes. Visually hidden in the styled tier.
  * @csspart table - The grid.
  *
- * @cssproperty --table-columns - Track list for the columns, which wins over the one the columns worked out.
+ * @cssproperty --table-columns - Track list for the columns. It overrides the track list worked out from the columns.
  */
 export declare class HelixTable extends HelixHeadlessTable {
     static styles: CSSResultGroup;

package/dist/table/row/table-row.d.ts

@@ -4,9 +4,9 @@ import type { CSSResultGroup } from 'lit';
  * @summary One row of a table.
  *
  * @description
- * No box of its own, so its cells become items of the table's grid and line up
- * with every other row's. The element still exists, which is what lets a row be
- * selected, hidden or made interactive without a wrapper that would break the
+ * The row has no box of its own, so its cells become items of the table's grid
+ * and line up with every other row. The element still exists, so a row can be
+ * selected, hidden, or made interactive without a wrapper that would break the
  * columns.
  *
  * @since 0.1.0

package/dist/tabs/panel/tab-panel.d.ts

@@ -4,9 +4,8 @@ import type { CSSResultGroup } from 'lit';
  * @summary The content shown for one tab.
  *
  * @description
- * No box of its own, so only the panel that is showing takes space: a tab set
- * with four panels gives the visible one the whole height rather than a
- * quarter of it.
+ * The panel has no box of its own, so only the panel that is showing takes
+ * space. In a set of four panels, the visible one gets the full height.
  *
  * @since 0.1.0
  * @status stable

package/dist/tabs/root/tabs-root.d.ts

@@ -4,24 +4,25 @@ import type { CSSResultGroup } from 'lit';
  * @summary A row of tabs and the panel each one shows.
  *
  * @description
- * One mark travels between the tabs rather than each of them filling and
- * emptying in turn. A fill that swaps is two things changing at once and reads
- * as a flicker; one that moves is a single object the eye follows, and it says
- * where the current tab was as well as where it is. `Navigation` marks its
- * destinations the same way and for the same reason.
+ * One mark moves between the tabs to show the current one. A moving mark is a
+ * single object that is easy to follow, and it shows where the selection came
+ * from. A fill that switches from tab to tab changes two things at once and
+ * looks like a flicker. `Navigation` marks its destinations the same way.
  *
- * What the mark is depends on `variant`: unset it is a raised pill on the
- * selected tab with nothing behind the row, `underlined` makes it a bar along
- * the bottom of the strip on a rule, and `segmented` grows it to the tab's own
- * box inside a sunken track.
+ * The mark depends on `variant`:
+ *
+ * - Unset, it is a raised pill on the selected tab, with nothing behind the
+ *   row.
+ * - `underlined` makes it a bar along the bottom of the strip, on a rule.
+ * - `segmented` makes it the size of the tab's box, inside a sunken track.
  *
  * @since 0.1.0
  * @status stable
  * @category navigation
  * @documentation https://fusion.dev/helix/components/tabs
  *
- * @slot - The tabs, which are this element's own children.
- * @slot panels - The panels, which are this element's own children. A wrapper around them is assigned to the slot and pairs with nothing, since the pairing walks these children rather than the slot's tree.
+ * @slot - The tabs, as direct children of this element.
+ * @slot panels - The panels, as direct children of this element. Panels inside a wrapper are not paired with tabs, because pairing reads only the direct children.
  *
  * @csspart panels - The panel container.
  * @csspart tabs - The tab list.

package/dist/tabs/tab/tab.d.ts

@@ -4,10 +4,10 @@ import type { CSSResultGroup } from 'lit';
  * @summary One tab in a tab list.
  *
  * @description
- * A control's height, so a tab row sits level with the buttons beside it. The
- * current tab is not marked here: one indicator travels along the tab list, and
- * each tab keeps a transparent edge of the same width so its box does not move
- * when it becomes current.
+ * A tab has a control's height, so a tab row sits level with the buttons beside
+ * it. The current tab is marked by one indicator that moves along the tab list.
+ * Each tab keeps a transparent edge of the same width, so its box does not
+ * shift when it becomes current.
  *
  * @since 0.1.0
  * @status stable

package/dist/tag/root/tag-root.d.ts

@@ -1,12 +1,11 @@
 import { HelixHeadlessTag } from '@fusion.dev/helix-headless/tag';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary Labels content with a short piece of metadata.
+ * @summary A short label that adds metadata to content.
  *
  * @description
- * Seven tones. The fill is a tint of the status color, mixed with
- * `color-mix` rather than held as a token per status, so a theme that changes
- * the status colors gets the tints with them.
+ * Seven tones. The fill is a tint of the status color made with `color-mix`, so
+ * when a theme changes its status colors, the tints change with them.
  *
  * @since 0.1.0
  * @status stable
@@ -16,18 +15,18 @@ import type { CSSResultGroup } from 'lit';
  *
  * @slot - The tag's label.
  *
- * @event {HelixDismissEvent} helix-dismiss - Fired when the reader asks to remove the tag. Cancelable: refusing it takes the decision and nothing moves.
+ * @event {HelixDismissEvent} helix-dismiss - The remove button was pressed. The tag does not remove itself, so remove it in response. Cancelable.
  *
  * @csspart dismiss - The remove button, when `dismissible`.
  *
- * @cssproperty --tag-background-color - Fill behind the tag.
- * @cssproperty --tag-border-color - Color of the edge, for a chip that separates by fill alone.
- * @cssproperty --tag-foreground-color - Label color.
- * @cssproperty --tag-radius - Corner radius of the tag.
+ * @cssproperty --tag-background-color - The fill behind the tag.
+ * @cssproperty --tag-border-color - The color of the tag's edge.
+ * @cssproperty --tag-foreground-color - The label color.
+ * @cssproperty --tag-radius - The corner radius of the tag.
  */
 export declare class HelixTag extends HelixHeadlessTag {
     /**
-     * How much of the tone the tag wears.
+     * How strongly the tag shows its tone: `subtle`, `solid`, or `outlined`.
      *
      * - `subtle` is the default: a wash of the tone with the label in it, for a
      *   tag that labels something rather than warning about it.
@@ -42,7 +41,7 @@ export declare class HelixTag extends HelixHeadlessTag {
      */
     emphasis?: 'outlined' | 'solid' | 'subtle';
     /**
-     * Which status the tag reports.
+     * The meaning the tag's color shows, such as `success` or `danger`.
      *
      * `tone` is semantic color, which is what these are and what `helix-text`
      * already calls them. `helix component`'s `axes` holds the vocabulary.

package/dist/text/root/text-root.d.ts

@@ -1,36 +1,29 @@
 import { HelixElement } from '@fusion.dev/helix-core';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary A run of text, with the element and the look chosen separately.
+ * @summary Text, with its HTML element and its type style set separately.
  *
  * @description
- * Two properties, and they answer different questions. `as` is the element,
- * which decides the document outline and what a screen reader announces.
- * `variant` is the ramp, which decides size, weight, leading, and tracking
- * together.
+ * `as` sets the element, which decides the document outline and what a screen
+ * reader announces. `variant` sets the type ramp, which decides size, weight,
+ * leading, and tracking together.
  *
- * They are separate because they genuinely come apart: a section's second
- * heading sometimes has to look smaller without lying about the outline, and a
- * `<p>` sometimes has to read as a caption. They default to matching, so the
- * common case is `as="h2"` and nothing else.
+ * The two match by default, so usually you set only `as`, such as `as="h2"`.
+ * Set `variant` when the look and the element differ, such as a heading that
+ * looks smaller or a `<p>` styled as a caption.
  *
- * The pairing is resolved in CSS rather than by computing an attribute, so the
- * element writes nothing to its own host: `as="h2"` picks up the heading ramp
- * through a selector, and setting `variant` takes the pairing rule out of play.
- * Deriving it in `willUpdate` works and must not be done: it puts an attribute
- * on the host that the server's markup does not have, which is a hydration
- * mismatch in every React consumer.
+ * The pairing is resolved in CSS, so the element writes nothing to its host.
+ * `as="h2"` picks up the heading ramp through a selector, and setting `variant`
+ * overrides the pairing. Do not derive it in `willUpdate`, because that adds a
+ * host attribute the server markup does not have, which causes a hydration
+ * mismatch in React.
  *
- * **Size, weight, and leading are not properties.** Exposing them separately
- * offers a few hundred combinations of which a handful are right, and every
- * caller then picks one. A ramp is a decision the system already made:
- * the ramp is named, and a page built from it is consistent because there was
- * nothing else to choose.
+ * Size, weight, and leading are not separate properties. Choose a named ramp
+ * with `variant`.
  *
- * `tone` and `emphasis` stay separate, because color carries state rather than
- * typography, and what a line means is not how loudly it says it. Folding
- * either in would mean `caption-danger` and `label-muted` and the rest of the
- * cross product, which is the explosion a named ramp exists to prevent.
+ * `tone` and `emphasis` are separate from `variant`, because color carries
+ * state. Combining them would need a variant for every pair, such as
+ * `caption-danger` and `label-muted`.
  *
  * @since 0.1.0
  * @status stable
@@ -44,13 +37,13 @@ import type { CSSResultGroup } from 'lit';
  */
 export declare class HelixText extends HelixElement {
     /**
-     * Which element to render.
+     * The HTML element to render.
      *
      * Decides the outline and the semantics.
      */
     as?: 'span' | 'p' | 'h1' | 'h2' | 'h3' | 'h4' | 'h5' | 'h6' | 'strong' | 'em' | 'code' | 'label';
     /**
-     * How loud the text is, beside what it means.
+     * Makes the text quieter: `muted`, or the quieter `subtle`.
      *
      * `muted` is the quiet ink that still has to be read, and `subtle` the
      * quieter one below it. Two axes because the test says so: a line can be a
@@ -67,9 +60,8 @@ export declare class HelixText extends HelixElement {
      */
     emphasis?: 'muted' | 'subtle';
     /**
-     * What the text means. A separate axis from the type ramp, because color
-     * carries state: folding it in would mean `caption-danger` and the rest of the
-     * cross product.
+     * The meaning of the text, shown by its color, such as `danger` or `success`.
+     * It is set separately from `variant`.
      *
      * **There is no `default` value**, and one must not be added: it would match
      * no rule and fall through to the inherited ink, reading as working while
@@ -80,7 +72,7 @@ export declare class HelixText extends HelixElement {
      */
     tone?: 'accent' | 'danger' | 'info' | 'primary' | 'success' | 'warning';
     /**
-     * Type treatment.
+     * The type style, which sets the size, weight, leading, and tracking.
      *
      * Defaults to the one that matches `as`.
      */

package/dist/textarea/root/textarea-root.d.ts

@@ -1,13 +1,12 @@
 import { HelixHeadlessTextarea } from '@fusion.dev/helix-headless/textarea';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary Several lines of text a reader types into.
+ * @summary A multi-line text field.
  *
  * @description
- * The same frame an `Input` wears, so a form of mixed fields reads as one set
- * rather than as two kinds of box. What differs is the resize handle, which is
- * the platform's and is left alone on the block axis only: a field that can be
- * dragged wider than the form holding it is a field that breaks the layout.
+ * Uses the same frame as `Input`, so mixed fields in a form match. The
+ * platform's resize handle is kept on the block axis only, so the field cannot
+ * be dragged wider than its form.
  *
  * @since 0.1.0
  * @status stable

package/dist/time-input/root/time-input-root.d.ts

@@ -4,18 +4,16 @@ import '../../icon/index.js';
 import '../../tag/index.js';
 import '../../time-picker/index.js';
 /**
- * @summary A time, typed or picked from a list.
+ * @summary A field for a time, typed or picked from a list.
  *
  * @description
- * The frame is the field rather than the input, so the trigger sits inside the
- * same box as the text and the focus ring is drawn once around the whole
- * control. The trigger is a mark within that box rather than a button beside it,
- * the arrangement Date Input settled on.
+ * The frame wraps the whole field, so the trigger sits in the same box as the
+ * text and the focus ring goes around the whole control. The trigger is drawn
+ * inside that box, as in Date Input.
  *
- * The panel is the field's width, which is the one place this differs from Input
- * Date: a calendar is seven columns with a width of its own, and a list of times
- * is a column of one line each, so it should be as wide as the control it
- * belongs to. That is the same reasoning Select gives for its own list.
+ * The panel is as wide as the field. This is the one difference from Input
+ * Date, whose calendar has seven columns and a width of its own. A list of
+ * times is one column, so it matches the control, as Select's list does.
  *
  * @since 0.1.0
  * @status stable
@@ -25,11 +23,11 @@ import '../../time-picker/index.js';
  *
  * @cssproperty --time-input-background-color - Fill behind the field.
  * @cssproperty --time-input-border-color - Color of the panel's edge.
- * @cssproperty --time-input-border-width - Width of the panel's edge. Follows
- *   `--helix-border-floating`, which is `0`, so the panel is told apart by its lift unless a
- *   theme says otherwise.
- * @cssproperty --time-input-shadow - Lift under the panel. Follows `--helix-shadow-floating`:
- *   a floating surface sits over content nobody can predict, so it keeps a lift by default.
+ * @cssproperty --time-input-border-width - Width of the panel's edge. Defaults to
+ *   `--helix-border-floating`, which is `0`, so the panel stands out by its shadow unless
+ *   your theme sets a width.
+ * @cssproperty --time-input-shadow - Shadow under the panel. Defaults to
+ *   `--helix-shadow-floating`, because the panel can sit over any content.
  */
 export declare class HelixTimeInput extends HelixHeadlessTimeInput {
     static tier: string;

package/dist/time-picker/root/time-picker-root.d.ts

@@ -3,17 +3,15 @@ import type { CSSResultGroup } from 'lit';
 import '../../listbox/index.js';
 import '../../option/index.js';
 /**
- * @summary Picks a time, from a list of them.
+ * @summary A control for choosing a time from a list or from wheels.
  *
  * @description
- * A bounded list on a surface of its own, because ninety-six rows is taller than
- * anywhere it will be put. `--time-picker-list-block-size` is the bound and it is a height
- * rather than a count of rows: what a panel has is room, and a row count would
- * have to be recomputed every time the density changed.
+ * The list has a bounded height on a surface of its own, because 96 rows are
+ * taller than any place it is used. `--time-picker-list-block-size` sets the
+ * bound as a height, so it does not need recomputing when the density changes.
  *
- * No border and no fill of its own. Flat on a page it takes what it is given,
- * and in Time Input's panel the panel supplies both: a list that brought its own
- * card would be a card inside a card there.
+ * The picker has no border or fill of its own. On a page it takes the space it
+ * is given, and inside Time Input the panel supplies both.
  *
  * @since 0.1.0
  * @status stable
@@ -22,8 +20,8 @@ import '../../option/index.js';
  * @documentation https://fusion.dev/helix/components/time-picker
  *
  * @cssproperty --time-picker-list-block-size - How tall the list is before it scrolls.
- * @cssproperty --time-picker-range-color - Wash behind the times inside a range.
- * @cssproperty --time-picker-row-size - Height and least width of one row in a wheel.
+ * @cssproperty --time-picker-range-color - Fill behind the times inside a range.
+ * @cssproperty --time-picker-row-size - Height and minimum width of one row in a wheel.
  * @cssproperty --time-picker-selected-color - Fill on the chosen row of a wheel.
  * @cssproperty --time-picker-wheel-block-size - How tall a wheel is. Five rows by default.
  */

package/dist/timeline/item/timeline-item.d.ts

@@ -4,8 +4,8 @@ import type { CSSResultGroup } from 'lit';
  * @summary One event on a timeline: when it happened, and what it was.
  *
  * @description
- * Presentation only: the rail down the side, the mark on it, and the line that
- * arrives at this entry from the one before.
+ * Draws the rail down the side, the mark on it, and the line that arrives from
+ * the previous entry.
  *
  * @since 0.1.0
  * @status stable

package/dist/timeline/root/timeline-root.d.ts

@@ -1,11 +1,11 @@
 import { HelixHeadlessTimeline } from '@fusion.dev/helix-headless/timeline';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary A record of what happened, in the order it happened.
+ * @summary A list of events, in the order they happened.
  *
  * @description
- * Presentation only: the direction time runs in, and the spacing between one
- * event and the next. Every entry draws its own mark and its own line.
+ * Sets the direction time runs in and the spacing between events. Each entry
+ * draws its own mark and line.
  *
  * @since 0.1.0
  * @status stable

package/dist/toast/item/toast-item.d.ts

@@ -4,10 +4,9 @@ import type { CSSResultGroup } from 'lit';
  * @summary One message in the toast region.
  *
  * @description
- * A surface with a shadow, because a toast sits over whatever the reader was
- * looking at rather than in it. The severity is a bar down the leading edge and
- * not a fill: a message is text to be read, and a colored panel behind it
- * costs contrast for something the mark already says.
+ * A surface with a shadow, because a toast sits over the page content. The
+ * severity is a bar along the leading edge, so the message text keeps full
+ * contrast on the surface.
  *
  * @since 0.1.0
  * @status stable
@@ -15,11 +14,11 @@ import type { CSSResultGroup } from 'lit';
  *
  * @cssproperty --toast-border-color - Color of the panel's edge.
  * @cssproperty --toast-border-width - Width of the panel's edge. Follows
- *   `--helix-border-floating`, which is `0`, so the panel is told apart by its lift unless a
- *   theme says otherwise.
+ *   `--helix-border-floating`, which is `0`, so the panel stands out by its shadow unless your
+ *   theme sets a border.
  * @cssproperty --toast-item-padding - Space between the message's edge and its contents.
- * @cssproperty --toast-shadow - Lift under the panel. Follows `--helix-shadow-floating`: a
- *   floating surface sits over content nobody can predict, so it keeps a lift by default.
+ * @cssproperty --toast-shadow - Shadow under the panel. Follows `--helix-shadow-floating`. A
+ *   floating surface can sit over any content, so it has a shadow by default.
  */
 export declare class HelixToastItem extends HelixHeadlessToastItem {
     static styles: CSSResultGroup;

package/dist/toast/root/toast-root.d.ts

@@ -1,21 +1,19 @@
 import { HelixHeadlessToast } from '@fusion.dev/helix-headless/toast';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary The region messages arrive in, and the only thing that announces them.
+ * @summary The region that holds toast messages, and the only element that announces them.
  *
  * @description
- * Fixed to the window, and it catches nothing: the region spans a whole edge,
- * so a stack of one message in a corner would otherwise put an invisible bar
- * across everything beside it. The region is transparent to a pointer and the
- * messages take it back.
+ * Fixed to the window. The region spans a whole edge, so it ignores the pointer
+ * and only the messages receive clicks. Content beside a message stays
+ * clickable.
  *
- * **It belongs at the root of the application.** `position: fixed` is
- * positioned against the viewport only while no ancestor carries `transform`,
- * `filter`, `perspective` or `contain`, any of which makes that ancestor the
- * containing block instead, and it is still clipped by an ancestor with
- * `overflow: hidden`. That is a real constraint rather than a style note, and
- * it is the same fact that put every other floating surface in this library
- * into the top layer.
+ * **Place the region at the root of your application.** `position: fixed`
+ * positions against the viewport only while no ancestor has `transform`,
+ * `filter`, `perspective`, or `contain`. Any of these makes that ancestor the
+ * containing block, and an ancestor with `overflow: hidden` still clips the
+ * region. The other floating surfaces in Helix use the top layer for the same
+ * reason.
  *
  * @since 0.1.0
  * @status stable

package/dist/toggle/group/toggle-group.d.ts

@@ -4,15 +4,13 @@ import type { CSSResultGroup } from 'lit';
  * @summary A row of options with the selection marked by a moving indicator.
  *
  * @description
- * The indicator travels between items rather than the fill swapping. A fill
- * that appears on one item as it disappears from another is two changes at once
- * and reads as a flicker; one object moving is something the eye follows, and
- * it says where the selection came from as well as where it went.
+ * The indicator moves between items, so a change of selection is one moving
+ * object the eye can follow.
  *
- * It animates `translate` and `inline-size`. Width is a layout property and the
- * rule is transform and opacity only, but the indicator is out of flow, so
- * animating its width reflows nothing else. Scaling instead would distort the
- * corner radius, which is worse than the exception.
+ * It animates `translate` and `inline-size`. Animating width is an exception to
+ * the transform and opacity rule, and it is safe because the indicator is out
+ * of flow and its width reflows nothing else. Scaling would distort the corner
+ * radius.
  *
  * @since 0.1.0
  * @status stable
@@ -20,16 +18,16 @@ import type { CSSResultGroup } from 'lit';
  * @documentation https://fusion.dev/helix/components/toggle
  *
  * @slot - The group's items.
- * @slot end - Whatever sits after the track on its own line, such as a count or a reset.
- * @slot start - Whatever sits before the track on its own line, such as an icon or a caption.
+ * @slot end - Content after the track, on the same line, such as a count or a reset.
+ * @slot start - Content before the track, on the same line, such as an icon or a caption.
  *
  * @csspart indicator - The moving marker behind the selected item.
  *
- * @cssproperty --toggle-group-indicator-color - Fill of the moving marker.
+ * @cssproperty --toggle-group-indicator-color - The fill of the moving marker.
  */
 export declare class HelixToggleGroup extends HelixHeadlessToggleGroup {
     /**
-     * How the group separates itself from the page.
+     * How the group is set apart from the page.
      *
      * Separation rather than emphasis, because what `plain` drops is the
      * background *and* the border: the question is where the group ends, not how

package/dist/toggle/root/toggle-root.d.ts

@@ -4,9 +4,8 @@ import type { CSSResultGroup } from 'lit';
  * @summary One option in a toggle group.
  *
  * @description
- * Carries no background of its own. The selected look comes from the group's
- * indicator sitting behind it, which is what lets that marker travel instead of
- * one fill appearing as another disappears.
+ * Has no background of its own. The selected look comes from the group's
+ * indicator behind it, which moves between items.
  *
  * @since 0.1.0
  * @status stable

package/dist/toolbar/root/toolbar-root.d.ts

@@ -4,8 +4,8 @@ import type { CSSResultGroup } from 'lit';
  * @summary A group of controls that share one tab stop.
  *
  * @description
- * No chrome of its own: a toolbar is a place controls sit, and a border around
- * them would be a second frame inside whatever already frames the bar.
+ * The toolbar draws no frame of its own, so it does not add a second frame
+ * inside whatever already frames the bar.
  *
  * @since 0.1.0
  * @status stable
@@ -17,7 +17,7 @@ import type { CSSResultGroup } from 'lit';
  *
  * @csspart toolbar - The toolbar container.
  *
- * @cssproperty --toolbar-gap - Space between controls.
+ * @cssproperty --toolbar-gap - The space between controls.
  */
 export declare class HelixToolbar extends HelixHeadlessToolbar {
     static styles: CSSResultGroup;

package/dist/tooltip/root/tooltip-root.d.ts

@@ -1,14 +1,14 @@
 import { HelixHeadlessTooltip } from '@fusion.dev/helix-headless/tooltip';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary A short description that appears beside what it describes.
+ * @summary A short text that appears next to an element on hover and focus.
  *
  * @description
- * The bubble is in the top layer, so it needs no `z-index` and cannot be
- * clipped by whatever it sits inside.
+ * The bubble is in the top layer, so it needs no `z-index` and no container
+ * clips it.
  *
- * The arrow is positioned by the same pass that positions the bubble, so it
- * still points at the trigger after the bubble has slid along to stay in view.
+ * The arrow is positioned in the same pass as the bubble, so it still points at
+ * the trigger after the bubble shifts to stay in view.
  *
  * @since 0.1.0
  * @status stable
@@ -17,14 +17,14 @@ import type { CSSResultGroup } from 'lit';
  * @aliases Hint, Popup label
  * @documentation https://fusion.dev/helix/components/tooltip
  *
- * @cssproperty --tooltip-arrow-size - Size of the point at the bubble's edge.
- * @cssproperty --tooltip-backdrop - Blur behind a `frosted` or `glass` bubble.
- * @cssproperty --tooltip-background-color - Fill of the bubble.
- * @cssproperty --tooltip-max-inline-size - Widest the bubble grows before wrapping.
+ * @cssproperty --tooltip-arrow-size - The size of the arrow on the bubble's edge.
+ * @cssproperty --tooltip-backdrop - The blur behind a `frosted` or `glass` bubble.
+ * @cssproperty --tooltip-background-color - The fill of the bubble.
+ * @cssproperty --tooltip-max-inline-size - The widest the bubble grows before its text wraps.
  */
 export declare class HelixTooltip extends HelixHeadlessTooltip {
     /**
-     * What the bubble is made of.
+     * The bubble's surface: `frosted` or `glass`.
      *
      * Absent is the inverse bubble, a dark surface over a light page, which is
      * what a hint over content the theme cannot know has always been here. `glass`

package/dist/tour/root/tour-root.d.ts

@@ -1,20 +1,19 @@
 import { HelixHeadlessTour } from '@fusion.dev/helix-headless/tour';
 import type { CSSResultGroup } from 'lit';
 /**
- * @summary A guided run through an interface, one stop at a time.
+ * @summary A guided tour of an interface, one stop at a time.
  *
  * @description
- * It draws the light and nothing else: the scrim's color and the lit box's
- * corners are this tier's, and the order, the stops and the measuring stay
- * below.
+ * Draws the spotlight: the scrim's color and the corners of the lit box. The
+ * order, the stops, and the measuring are in the headless tier.
  *
  * @since 0.1.0
  * @status stable
  * @category overlays
  * @documentation https://fusion.dev/helix/components/tour
  *
- * @cssproperty --tour-scrim-color - The darkness outside the lit box.
- * @cssproperty --tour-spotlight-radius - Corner radius of the lit box.
+ * @cssproperty --tour-scrim-color - The color of the dimmed area outside the spotlight.
+ * @cssproperty --tour-spotlight-radius - The corner radius of the spotlight.
  */
 export declare class HelixTour extends HelixHeadlessTour {
     static styles: CSSResultGroup;