@amyegan sorry for direct tag, but do you know if anyone will take a look? Doc issues must be treated seriously imho, especially for a major framework

@pawlean Hello, can you please explain why did you move this post from discussions to here? I could not find description of topics for "discussions" to conclude that this was not on topic there. I see people there talk there about all sorts of things.

Hey @gmaniava! Your topic was moved because it relates to an open source project rather than general Vercel features. It's not hidden, just recategorized so it's easier to find by people most likely to be interested in the topic.

Appreciate you sharing feedback on the docs! It's been shared internally, and the Next.js and documentation folks will review as soon as they're able.

Ok, if you moved it so be it, I thought there it had better visibility. But if you shared internally and they will look at it and give consideration that is the most important thing. Please see this, I am not sharing this to advertise my post, just it is very relevant for nextjs docs! PS. Those are not the only two issues I have opened or encountered!

Apologises for causing any stress, @gmoniava! I thought that moving your post would bring more visibility to our already very busy forum and especially that category.

Great post by the way, we're doing the best we can to make sure these issues are flagged. Thank you again for being part of the community!

it's ok. If you are referring to my blog post thanks and btw that post is very relevant for Nextjs docs. I hope the team will not ignore those two gh issues. It is really not ok for a major framework like Nextjs to have such flaws in the docs. And this is not the first time I encountered such problems. I think Vercel must do smth. to more seriously take a look at their docs!