From ec25aeb34fdbfca2ffcbe5f70740485dc8eebbc7 Mon Sep 17 00:00:00 2001 From: Mirror <113173672+Mirror-Tang@users.noreply.github.com> Date: Sun, 10 Sep 2023 02:01:45 +0800 Subject: [PATCH] docs: Fix challenge failure caused by case errors in client-side.mdx (#1433) --- docs/pages/client-side.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pages/client-side.mdx b/docs/pages/client-side.mdx index ce535a6431..287cd1b939 100644 --- a/docs/pages/client-side.mdx +++ b/docs/pages/client-side.mdx @@ -8,8 +8,8 @@ There also exists tooling for [Unity](https://github.com/emergenceland/unimud) f ## Representing state in the browser -Currently the way to query the [Store](/Store) and react to changes is `recs`. -This package is designed to represent and query ECS data from a [`Store`](/Store). +Currently the way to query the [Store](/store) and react to changes is `recs`. +This package is designed to represent and query ECS data from a [`Store`](/store). If your MUD tables are set up with a single `bytes32` key (see the [ECS modelling guide](/ecs)), and you plan to represent an entity and its associated components as the same `bytes32` key on multiple tables, then `recs` will let you query your data in a natural way. To read data and react to changes with `recs`, there exists two APIs: