fix typo in directory name

[timdeschryver]

Coming from #27865 (comment)

This PR fixes a typo in the directory name (diagonstics => diagnostics).
After this PR, the "base" is good to pick up the other issues without interrupting each other.

Should be merged together with dotnet/AspNetCore.Docs.Samples#192

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/fundamentals/aot/request-delegate-generator/diagnostics/rg002.md	RDG002: Unable to resolve endpoint handler

[Rick-Anderson]

@tdykstra had the same comment, I'm not seeing that. https://learn.microsoft.com/en-us/aspnet/core/fundamentals/aot/request-delegate-generator/diagnostics/rdg002?view=aspnetcore-8.0 is rendering correctly and you version isn't finding the snippets.

[Rick-Anderson]

From the build report

I do have to change the UID on all these from rdgxxx to rgxxx per the source code.

[timdeschryver]

The reason why it's rendered correctly on the live learn website is because the samples are added to the directory containing the typo (diagonstics).
In other words, the typo exists within this repo and the samples repo.

The current state of this PR fails because it cannot find the snippets due to the rename within the docs, but not in the samples repo.

To fix the build (at least how I see it, and feel free to correct me), I think the PR of the samples repo needs be merged first (dotnet/AspNetCore.Docs.Samples#192) because it fixes the typo within that repo.

After the samples PR is merged this PR will successfully build because it can now find the files.

I tested this on my local machine (it works on my machine 😅)

[Rick-Anderson]

@timdeschryver can you change all the rdg00x to rg00x like I did in https://github.com/dotnet/AspNetCore.Docs/pull/30499/files, that will get rid of the merge conflict. I had to change that to generate the correct URL

[Rick-Anderson]

Actually, it's a file rename that needs to happen, drop the d in the file name

[timdeschryver]

Sorry, I was just leaving. Thanks for the fixup!

[Rick-Anderson]

Thanks for fixing this. @tdykstra notified me of the same problem and I couldn't see it, ha.