From 1c28f45911a26bb87234d0d0da3013ef590e8b09 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Birger=20Mo=C3=ABll?= Date: Mon, 12 Feb 2024 11:28:50 +0100 Subject: [PATCH] Fixed a typ with a missing word in the documentaiotn (#5169) Fixed a type. A word was missing in the docs. --- docs/content/concepts/entity-component.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/entity-component.md b/docs/content/concepts/entity-component.md index ede3a1c7e691..39ea923160d7 100644 --- a/docs/content/concepts/entity-component.md +++ b/docs/content/concepts/entity-component.md @@ -41,7 +41,7 @@ See the [Types](../reference/types.md) reference for a list of archetypes, compo ### Adding custom data -Although both the SDKs' archetype objects and the space view are based on the same archetype definition (and are actually implemented using code that is automatically generated based that definition), they both operate on arbitrary collection +Although both the SDKs' archetype objects and the space view are based on the same archetype definition (and are actually implemented using code that is automatically generated based on that definition), they both operate on arbitrary collection of components. Neither the SDKs nor the viewer enforce or require that an entity should contain a *specific* set of component. The Rerun viewer will display any data in a generic form, but its space views will only work on sets of components it can make sense of.