From f5f092f2f3909853c0e3ece2d5c55a91dc621650 Mon Sep 17 00:00:00 2001 From: Lucas Franca Date: Mon, 9 Jun 2025 19:55:14 -0300 Subject: [PATCH] Fix new typos (#19562) # Objective Fix new typos found on new version of `typos` (#19551) ## Solution Fix typos --- crates/bevy_ecs/src/component.rs | 2 +- release-content/migration-guides/entity_representation.md | 2 +- .../migration-guides/remove_deprecated_batch_spawning.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/crates/bevy_ecs/src/component.rs b/crates/bevy_ecs/src/component.rs index c4b8eec31d..96f0ffed9f 100644 --- a/crates/bevy_ecs/src/component.rs +++ b/crates/bevy_ecs/src/component.rs @@ -2053,7 +2053,7 @@ impl Components { } /// Gets the metadata associated with the given component, if it is registered. - /// This will return `None` if the id is not regiserted or is queued. + /// This will return `None` if the id is not registered or is queued. /// /// This will return an incorrect result if `id` did not come from the same world as `self`. It may return `None` or a garbage value. #[inline] diff --git a/release-content/migration-guides/entity_representation.md b/release-content/migration-guides/entity_representation.md index e042f493da..142b456b75 100644 --- a/release-content/migration-guides/entity_representation.md +++ b/release-content/migration-guides/entity_representation.md @@ -49,7 +49,7 @@ This means that where `Result` was returned, `Option` is It is well documented that both the bit format, serialization, and `Ord` implementations for `Entity` are subject to change between versions. Those have all changed in this version. -For entity ordering, the order still prioretizes an entity's generation, but after that, it now considers higher index entities less than lower index entities. +For entity ordering, the order still prioritizes an entity's generation, but after that, it now considers higher index entities less than lower index entities. The changes to serialization and the bit format are directly related. Effectively, this means that all serialized and transmuted entities will not work as expected and may crash. diff --git a/release-content/migration-guides/remove_deprecated_batch_spawning.md b/release-content/migration-guides/remove_deprecated_batch_spawning.md index 9ab5ab0bbf..1b17eba563 100644 --- a/release-content/migration-guides/remove_deprecated_batch_spawning.md +++ b/release-content/migration-guides/remove_deprecated_batch_spawning.md @@ -14,6 +14,6 @@ They were deprecated in 0.16 for being unnecessary with the retained render worl Instead of these functions consider doing one of the following: -Option A) Instead of despawing entities, insert the `Disabled` component, and instead of respawning them at particular ids, use `try_insert_batch` or `insert_batch` and remove `Disabled`. +Option A) Instead of despawning entities, insert the `Disabled` component, and instead of respawning them at particular ids, use `try_insert_batch` or `insert_batch` and remove `Disabled`. Option B) Instead of giving special meaning to an entity id, simply use `spawn_batch` and ensure entity references are valid when despawning.