mirror of
https://github.com/bevyengine/bevy
synced 2024-12-18 17:13:10 +00:00
Fix a couple typos (#16573)
# Objective Fix typo reported on [discord](https://discord.com/channels/691052431525675048/743559241461399582/1312485153284558932). ## Solution - Search for "will can." - Fix typo - Fix another related typo
This commit is contained in:
parent
eaa7dfedea
commit
c425c32064
2 changed files with 2 additions and 2 deletions
|
@ -413,7 +413,7 @@ impl BlobArray {
|
|||
self.get_unchecked_mut(index_to_keep).promote()
|
||||
}
|
||||
|
||||
/// This method will can [`Self::swap_remove_unchecked`] and drop the result.
|
||||
/// This method will call [`Self::swap_remove_unchecked`] and drop the result.
|
||||
///
|
||||
/// # Safety
|
||||
/// - `index_to_keep` must be safe to access (within the bounds of the length of the array).
|
||||
|
|
|
@ -9,7 +9,7 @@ use crate::{entity::Entity, query::ReadOnlyQueryData};
|
|||
///
|
||||
/// Infinite loops are possible, and are not checked for. While looping can be desirable in some contexts
|
||||
/// (for example, an observer that triggers itself multiple times before stopping), following an infinite
|
||||
/// traversal loop without an eventual exit will can your application to hang. Each implementer of `Traversal`
|
||||
/// traversal loop without an eventual exit will cause your application to hang. Each implementer of `Traversal`
|
||||
/// for documenting possible looping behavior, and consumers of those implementations are responsible for
|
||||
/// avoiding infinite loops in their code.
|
||||
///
|
||||
|
|
Loading…
Reference in a new issue