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

[Documentation Update]: Website bug - spec links #1846

Closed
1 task done
ReneHezser opened this issue Feb 7, 2025 · 1 comment · Fixed by #1877
Closed
1 task done

[Documentation Update]: Website bug - spec links #1846

ReneHezser opened this issue Feb 7, 2025 · 1 comment · Fixed by #1877
Assignees
Labels
Type: Bug 🐛 Something isn't working Type: Documentation 📄 Improvements or additions to documentation

Comments

@ReneHezser
Copy link
Contributor

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Description

The link in the specification tables, does not point to the actual spec.

Image

@ReneHezser ReneHezser added Needs: Triage 🔍 Maintainers need to triage still Type: Documentation 📄 Improvements or additions to documentation labels Feb 7, 2025
@github-project-automation github-project-automation bot moved this to Needs: Triage in AVM - Issue Triage Feb 7, 2025

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation.

@ReneHezser ReneHezser self-assigned this Feb 24, 2025
@ReneHezser ReneHezser added Type: Bug 🐛 Something isn't working and removed Needs: Triage 🔍 Maintainers need to triage still labels Feb 24, 2025
@github-project-automation github-project-automation bot moved this from Needs: Triage to Done in AVM - Issue Triage Feb 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug 🐛 Something isn't working Type: Documentation 📄 Improvements or additions to documentation
Projects
Development

Successfully merging a pull request may close this issue.

1 participant