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

[Grammar Adjustment] Tutorials - MeshMap Snapshots #208

Open
sandramsc opened this issue Feb 9, 2024 · 5 comments
Open

[Grammar Adjustment] Tutorials - MeshMap Snapshots #208

sandramsc opened this issue Feb 9, 2024 · 5 comments
Assignees
Labels
area/docs Improvements or additions to documentation framework/hugo good first issue Good for newcomers language/markdown

Comments

@sandramsc
Copy link
Member

sandramsc commented Feb 9, 2024

Current State:

  • Link to website: MeshMap Snapshot
  • Currently, the text in the sentences below have some grammar or spelling errors.
    l5

Desired State:
3. Use the multi-step connection wizard to authorize Meshery to access your GitHub repositories (you may need to sign into GitHub).
6. You will establish a secret for the Meshery GitHub app and a new workflow to be invoked when a new snapshot is needed.
6.1 Customize the workflow on event trigger to match your needs.


Contributor Guides and Resources

@sandramsc sandramsc added area/docs Improvements or additions to documentation good first issue Good for newcomers language/markdown framework/hugo labels Feb 9, 2024
@sandramsc
Copy link
Member Author

sandramsc commented Feb 9, 2024

Discuss:

  • It could be that the word on in point 6.1 is in the current format because its purpose is to convey a state (i.e inside a code block)

@PersonaMate
Copy link

PersonaMate commented Apr 12, 2024

Hey @sandramsc, I am new to the community and would like to work on this simple issue to get started.

@sandramsc
Copy link
Member Author

@PersonaMate Welcome to the community, I have assigned this to you.

@PersonaMate
Copy link

PersonaMate commented Apr 13, 2024

@sandramsc,

Discuss:

It could be that the word on in point 6.1 is in the current format because its purpose is to convey a state (i.e. inside a code block)

..... So should I leave it as it is or make it as you mentioned in the desired state? (For 6.1)

@leecalcote
Copy link
Member

Bump

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/docs Improvements or additions to documentation framework/hugo good first issue Good for newcomers language/markdown
Development

No branches or pull requests

3 participants