🦉Doc Corrections

I was emotional and wrong. After revisiting multiple other chats, all of
them do it this way. Adding reactions to existing ones was what I was
missing. the first reaction can be in the top right bar.

owl/README.md

@@ -14,7 +14,7 @@ In this owl folder should go all documents we produce for this Endeavour.
 
  - Find a way to build extensions that survive upstream merges best. This means, reduce contact point, create own files, even be in own folder if possible. This needs a thorough scan of the codebase.
  - We will try to integrate `comms` project at some point. but this is a separate task, not needed yet. It will bring voice server to the rooms. comms uses a wasm system.
- - Try to find out how much we can change behaviour of the page with the _themes_ (skins) only. Some small silly things, like that reacting with a new emoji on a post should not be on the left side of a message, where currently it is embedded in a popup. Who makes such terrible UX Decisions anyway; same about some of the icons or menus, that are just confusing overengineered element crap.
+ - Try to find out how much we can change behaviour of the page with the _themes_ (skins) only. Some small silly things, like that reacting with a new emoji on a post should not be on the left side of a message, where currently it is embedded in a popup.
  - Find out how we can set that Twitter Emojis are standard - system emojis on windows are terrible.
  - Find out how we can set a theme by default for new users.
  - img tags in messages should be rendered, without requiring them to be on a local cache. We do not need to secure against identification attacks.