diff --git a/README.md b/README.md
index 4f60e75..f1b5617 100644
--- a/README.md
+++ b/README.md
@@ -110,7 +110,7 @@ fn show_tooltips(
 ```
 
 Alternatively, if you expect to only have component implementing the trait for each entity,
-you can use the filter [`One`](https://docs.rs/bevy-trait-query/latest/bevy_trait_query/struct.One.html). This has significantly better performance than iterating
+you can use the filter [`One`](https://docs.rs/bevy-trait-query/latest/bevy_trait_query/one/struct.One.html). This has significantly better performance than iterating
 over all trait impls.
 
 ```rust
diff --git a/src/lib.rs b/src/lib.rs
index 9febcca..cf3de8c 100644
--- a/src/lib.rs
+++ b/src/lib.rs
@@ -164,7 +164,7 @@
 //! ```
 //!
 //! Alternatively, if you expect to only have component implementing the trait for each entity,
-//! you can use the filter [`One`](crate::One). This has significantly better performance than iterating
+//! you can use the filter [`One`](crate::one::One). This has significantly better performance than iterating
 //! over all trait impls.
 //!
 //! ```ignore
@@ -189,21 +189,6 @@
 //! # bevy::ecs::system::assert_is_system(show_tooltips);
 //! ```
 //!
-//! Trait queries support basic change detection filtration. So to get all the components that
-//! implement the target trait, and have also changed in some way since the last tick, you can:
-//! ```ignore
-//! fn show_tooltips(
-//!     tooltips: Query<ChangedAll<&dyn Tooltip>>
-//!     // ...
-//! ) {
-//!     for tooltip in &tooltips {
-//!         println!("changed tool tips: {}", tooltip.tooltip());
-//!     }
-//! }
-//! ```
-//!
-//! Similarly, there exist `ChangedOne`, `AddedOne`, and `AddedAll`.
-//!
 //! # Performance
 //!
 //! The performance of trait queries is quite competitive. Here are some benchmarks for simple cases: