MariaPaula Trujillo

Oh also, forgot to mention this above, but the "latest toolchains" link routes to this same page which seems a bit weird. I left a [comment](https://docs.google.com/document/d/1VJ3xT2ViC-CvL0UmsAUzpYFmvpuqUP4AbpnlPm8tqOA/edit?disco=AAAAgslIFbo) in the doc asking...

@pmahnke @xnox are we free to close this?

Thanks for taking this on @stonepreston and @kwmonroe! Could you update the [copy doc](https://docs.google.com/document/d/1-l3B7AoyDoETaL80UhlfEWCVKmMWPdy3zoF5LpsGcYQ/edit) to reflect these changes as well? Usually changes are made there first and then requested for...

Hi @stonepreston , is this ready for review?

No worries @evilnick! I'll move this out of the review/qa pipeline for now then 🙂

@carkod I was going by what was on the [spreadsheet](https://docs.google.com/spreadsheets/d/1YeTZP9sr2WUX2-N7clirZtGuARD0PMirHk0Ty-WUKU0/edit#gid=987317135) that Dave left. But it does sound weird that they would all link to "How to write a tutorial" now...

Hi @pprincipeza. It would require a bit more work than just adding it to the CVE pages, although nothing too crazy I don't think. We currently do not have this...

@davegoddard42 Not hard at all, we can just add an id to the heading and set that as the href. I tested it locally with a couple different sections just...

I've had this thought too, it does seem like it would make sense. But I when I was on my vanilla rotation I had to do an [accessibility write up...

I'm not quite sure if I'm missing something, but I'm not able to recreate this bug on ubuntu. Both Chrome and Firefox seem to work as expected: ![Screenshot from 2022-10-18...