Apply suggestions from code review

Co-authored-by: Chris Russell <8494645+chescock@users.noreply.github.com>

Author: ElliottjPierce

crates/bevy_ecs/src/query/state.rs

@@ -171,7 +171,7 @@ impl<D: QueryData, F: QueryFilter> QueryState<D, F> {
     ///
     /// This function may fail if, for example,
     /// the components that make up this query have not been registered into the world.
-    #[deprecated(since = "0.19.0", note = "Use `init_state` instead.")]
+    #[deprecated(since = "0.19.0", note = "Use `new` instead.")]
     pub fn try_new(world: &World) -> Option<Self> {
         let mut state = Self::try_new_uninitialized(world)?;
         state.update_archetypes(world);

crates/bevy_ecs/src/world/mod.rs

@@ -1746,7 +1746,7 @@ impl World {
     /// assert!(some_query.is_some());
     /// ```
     #[inline]
-    #[deprecated(since = "0.19.0", note = "Use `init_state` instead.")]
+    #[deprecated(since = "0.19.0", note = "Use `query` instead.")]
     #[expect(deprecated, reason = "also deprecated")]
     pub fn try_query<D: QueryData>(&self) -> Option<QueryState<D, ()>> {
         self.try_query_filtered::<D, ()>()
@@ -1775,7 +1775,7 @@ impl World {
     /// Requires only an immutable world reference, but may fail if, for example,
     /// the components that make up this query have not been registered into the world.
     #[inline]
-    #[deprecated(since = "0.19.0", note = "Use `init_state` instead.")]
+    #[deprecated(since = "0.19.0", note = "Use `query_filtered` instead.")]
     #[expect(deprecated, reason = "also deprecated")]
     pub fn try_query_filtered<D: QueryData, F: QueryFilter>(&self) -> Option<QueryState<D, F>> {
         QueryState::try_new(self)

release-content/release-notes/readonly_query_states.md

@@ -29,6 +29,6 @@ fn read_sub_world(sub_world: Res<MySubWorld>) {
 
 ```
 
-Note that using `World::query` or `QueryState::new` each time results in an uncached query.
+Note that using `World::query` or `QueryState::new` initializes a new query cache each time.
 The query state and matching tables must be recalculated each time.
 As a result, for queries that are running very frequently, caching the `QueryState` (through system parameters, for example) is still a good idea.