Skip to content

📝 Refine phrasing, fix typos, and improve clarity in documentation #255

@Dugyu

Description

@Dugyu

This issue tracks the refinement of language throughout the Lynx Living Spec. The goal is to fix typos, improve wording, and ensure consistent, professional documentation.

Typos

  • 2.3 Running Scenary to Running Scenarios

  • 4.4.2.2 performingelement to performing element

  • 7.1.1 "it is largely written in C++" to "It is largely written in C++"

  • 8.1.4 layou to layout

Wording

  • 3.3.1
    Original: "...abstracting away the threading strategy away from scripting developers."
    Suggested: "...abstracting the threading strategy away from scripting developers."
    (Removes redundant 'away' for clarity and fluency.)

  • 7.2.1
    Original: At this stage, based on the attribute of the element, the computed style and prop bundle of the element are generated and synchronized to the layout node. This stage will also create and modify layout node tree. At the same time, it will also generate UI paint op.
    Suggested: At this stage, the computed style and prop bundle are generated based on the element's attributes and synchronized to the layout node. Meanwhile, the layout node tree may be created or modified, and UI paint ops are emitted for rendering.
    (Avoids redundant phrasing and improves flow.)

  • 7.2.3
    Original: The act of executing the pixel pipeline. Try changes within the bundle’s structures...
    Suggested: The act of executing the pixel pipeline. Try making changes within the bundle’s structures...
    (Avoids unnatural phrase.)

Terminology consistency

  • 8.2.7.3
    Original: Element ITC is the inter thread call exposed to script developers in the BTS environment.
    Suggested: Element ITC is the inter thread call exposed to scripting framework developers in the BTS environment.
    (Avoids undefined and ambiguous terminology. scripting framework developers is defined in 1.2.2. )
    script developers is also used in 2.2.6, 4.3.3, 4.6, 8.2.7.2, 8.2.7.3, 8.2.7.4.

More refinements will follow in future PRs as we continue improving the clarity and consistency of the Living Spec. This issue serves as a central reference point for related language improvement efforts.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions