Description
Description
There are instances where a different adapter name is used in between the instruction of a different adapter. This might confuse people and further create problems to complete the lab. Attached is an example of what I am talking about. Need to change this mismatch on all the adapters that have this mistake.
Expected Behavior
The adapter name should be set correctly on the instruction.
Environment:
- Host OS: macOS
- Browser: Brave, Safari
Contributor Resources
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master
branch.
- See contributing instructions
- See Layer5 site designs in this Figma project.
Activity
welcome commentedon Dec 29, 2021
Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack.
leecalcote commentedon Dec 30, 2021
So good of you to open up this issue, @asubedy
asubedy commentedon Dec 30, 2021
@leecalcote the labs' screenshot seems to be outdated and does not match with the current meshery UI. The instructions too seem to be pointing to older text. Should I update these all in this issue only?
leecalcote commentedon Dec 30, 2021
@asubedy, yes, that'll work. The updates can be grouped together.
asubedy commentedon Dec 30, 2021
Yes, all right will be doing that too. 🚀
stale commentedon Feb 26, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon Mar 9, 2022
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.
leecalcote commentedon Mar 9, 2022
@asubedy are we all clear here (done)?
stale commentedon Apr 24, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stale commentedon May 5, 2022
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.