Typos

Open
#358 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
48/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript
Domain
documentation

Research direction

Open the source pages corresponding to https://developer.yoast.com/features/schema/technology-approach/ and https://developer.yoast.com/features/schema/functional-specification/. Find the two quoted typos, correct their wording, and verify that both published documentation pages display the intended text.

Written by the indexing model from the issue text.

Description

Please give us a description of the issue

On https://developer.yoast.com/features/schema/technology-approach/ there is a small typo:

For example, our Yoast WooCommerce SEO plugin relies on parsing product information which isn't available during initialization, and so outputs a secondary <script> blog in the page's footer

"<script> blog" should be "<script> block" or just "<script>"

On https://developer.yoast.com/features/schema/functional-specification/ there is a small typo

The support of other search engines (e.g., Baidu, Yandex, others) is unknown; it's our assumption that support will generated be limited, or not exist. We hope that the broad adoption of our approach will encourage these, and other consumers, to expand their support.

"support will generated be limited" should be "support will be limited" or, "support will generally be limited".

  • I've read and understood the contribution guidelines.
  • I've searched for any related issues and avoided creating a duplicate issue.
Dominant language
JavaScript
Stars
15
Forks
23
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Yoast/developer

All issues in Yoast/developer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.