[docs] Building with relationships article

[Riztazz]

Describe the bug
Throughout the documentation we're sent to the article ( https://ajmmertens.medium.com/building-games-in-ecs-with-entity-relationships-657275ba2c6c ) which states that we should view the live link demos (it does so multiple times).
The problem is that the links always point into same view, which i think is a bug as it contains no information about the topic we're reading about

To Reproduce
Steps to reproduce the behavior:

1. Go to (https://ajmmertens.medium.com/building-games-in-ecs-with-entity-relationships-657275ba2c6c)
2. Click on ' Live demo '
3. See the webpage it points to

Expected behavior
Possibly point into valid live demo or i've greatly misunderstood something :)

2nd)
As this is such a misc small thing, i'll keep it here as well
https://www.flecs.dev/flecs/md_docs_2Relationships.html
Near the part

The ability to share components is also applied transitively, so Frigate could be specialized further into a FastFrigate:

We're being shown getting the overriden value from FastFrigate - there is a typo i think, as it gets the component from base Frigate instead of the FastOne

[Riztazz]

https://www.flecs.dev/flecs/md_docs_2ObserversManual.html

near the part:

Events can be components, which makes it possible to add event-specific data:

The actual event in C++ code lacks the variables, seems like a typo - as they exist for C# and rust

[SanderMertens]

The problem is that the links always point into same view, which i think is a bug as it contains no information about the topic we're reading about

Yeah the links use an ability of the old v3 explorer to provide scripts in the URL. I almost got it working again in the v4 explorer but still needs a bit of work before the links work again.

[Riztazz]

Another little thing;

That's from Task part in Systems
From what i understand, the singleton() has been replaced with trait? so this seems dead doc

@SanderMertens if you would like me to move this out of issues, please let me know

[SanderMertens]

@Riztazz it's not good practice to list multiple unrelated issues on the same github issue. If you're finding a lot of things, maybe open a thread on the Discord, or create separate issues for them. Otherwise it becomes very difficult to keep track of what got fixed vs. what didn't.

For small doc fixes, people typically create a PR, which is a faster way to get it fixed!

[Riztazz]

Sure.

[SanderMertens]

I'm keeping this open for the original links/explorer issue.