@cohult Did you read the changes carfully? I am a documentation novice and didn't get that gitbook plugin for pretty code rendering to work.. So I hope formatting and styling looks proper.

@EdvinOlofsson , to spare us from checking formatting and styling, you can merge your markdown to the test-n-play branch and then to go to the gitbook editor for a preview: https://app.gitbook.com/o/zCWEO4HUVOjwxqT5Hla6/s/MCFXLJGKRQEW4n8TBkyC/development/advanced-development/web-ui-development/json-rpc-api
Although, you have five simple gitbook extensions in there, four "code title" and one "hint". They all look ok to me. The rest is generic markdown which the GitHub markdown renderer can preview for you.
https://github.com/NSO-developer/nso-gitbook/blob/eolofsso/ENG-37149-webui-doc/development/advanced-development/web-ui-development/README.md

@EdvinOlofsson , Also, since you are editing only a single Markdown page here and you want to preview the five GitBook extensions, next time I suggest you use the GitBook editor to make the changes. After you merged the changes done in the GitBook editor to main, you can get the commit id from here (GitHub) and cherry-pick when backporting to 6.6, 6.5, 6.4 etc branches.

I see your suggestions @cohult Thanks for the detailed tips!
Yes, I was only using github editor and previews... In the future I will try the Gitbook editor and test-n-play branch (smart idea!)

I've pushed PR feedback fixes now. (minor typos, thanks for reading carefully!)
When merging I plan to do squash-and-merge. Any special commit messages format or is this commit message good enough?:
[ENG-37149] Modernizing WeUI development documentation README.md file

@EdvinOlofsson, definitely good enough. The more we use the tailf repo type of commit messages and branch names the better. Good to point to the ENG ticket.