There is more and more stupidity in datasheets these days.
I have been working on a design that used an STM32 connected to an external NOR Flash using QSPI. Rather than using MOSI and MISO signals that are ubiquitous for SPI mode, some boofhead at ST decided to use SI and SO on both the STM and external flash chip app note on both the micro and the flash. And guess what? SI means Serial_In and SO means Serial_Out; not Slave_In and Slave_Out. So it is so easy to get the signals swapped, like the ubiquitous TX/RX dilemma. Nothing worse than ambiguity in a datasheet. MOSI and MISO were named as such for very good reasons.... to avoid confusion.
I think some tech writers out there have never worked as technicians or engineers. The best electronic design engineers tend to be those who have experience as debug or service technicians at some stage in their career. At least then they will understand the benefits of back annotating a PCB design during the early stages of a project, or having an accessible ground test point on the design. With mechanical engineers, the best are those who were brought up by their dads with a screwdriver in the hand or raised on a farm, because they are generally far more practically capable than someone who was brought up with servants or nannies.
There is some pleasure is reading TI, LT and AD datasheets
. These companies hire very good technical communicators and have good processes to get their datasheets right.