Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/website: blog post contains a typo #58951

Closed
mkraft opened this issue Mar 9, 2023 · 2 comments
Closed

x/website: blog post contains a typo #58951

mkraft opened this issue Mar 9, 2023 · 2 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. website
Milestone

Comments

@mkraft
Copy link

mkraft commented Mar 9, 2023

Typo in blog post.

URL: https://go.dev/blog/integration-test-coverage

Sentence:

This merge capability is also useful to combine results from different types of test runs, including runs from generated by other test harnesses.

Recommendation:

This merge capability is also useful to combine results from different types of test runs, including runs from generated by other test harnesses.

Alternatively:

This merge capability is also useful to combine results from different types of test runs, including runs from generated by other test harnesses.

@gopherbot gopherbot added this to the Unreleased milestone Mar 9, 2023
@mkraft mkraft changed the title x/website: x/website: Blog post typo. Mar 9, 2023
@cagedmantis cagedmantis added the NeedsFix The path to resolution is known, but the work has not been done. label Mar 9, 2023
@cagedmantis cagedmantis changed the title x/website: Blog post typo. x/website: blog post contains a typo Mar 9, 2023
@gopherbot
Copy link

Change https://go.dev/cl/474957 mentions this issue: _content/blog: fix a typo in the integration test coverage post

@cagedmantis
Copy link
Contributor

Thanks for reporting this @mkraft.

@golang golang locked and limited conversation to collaborators Mar 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done. website
Projects
None yet
Development

No branches or pull requests

3 participants