Normally, the documentation goes through neovim's inbuilt method to process used markdown with a centralized function. This function by default does basically the same as the original code, but when some other plugin takes on the chore to give a better representation of documentation markdown (noice.nvim or reform.nvim), it shouldn't have to replace every plugin's markdown processing, because they should use the inbuilt method first.
Normally, the documentation goes through neovim's inbuilt method to process used markdown with a centralized function. This function by default does basically the same as the original code, but when some other plugin takes on the chore to give a better representation of documentation markdown (noice.nvim or reform.nvim), it shouldn't have to replace every plugin's markdown processing, because they should use the inbuilt method first.