doc fixes

Cargo.toml

@@ -10,7 +10,6 @@ documentation = "https://docs.rs/crate/big_space/latest"
 
 [dependencies]
 bevy_app = { version = "0.13", default_features = false }
-bevy_derive = { version = "0.13", default_features = false }
 bevy_ecs = { version = "0.13", default_features = false }
 bevy_hierarchy = { version = "0.13", default_features = false }
 bevy_log = { version = "0.13", default_features = false }

src/bundles.rs

@@ -7,7 +7,7 @@ use bevy_transform::prelude::*;
 
 /// Minimal bundle needed to position an entity in floating origin space.
 ///
-/// This is the floating origin equivalent of the [`bevy::prelude::SpatialBundle`].
+/// This is the floating origin equivalent of the `bevy` `SpatialBundle`.
 #[derive(Bundle, Default)]
 pub struct BigSpatialBundle<P: GridPrecision> {
     /// The visibility of the entity.
@@ -27,10 +27,10 @@ pub struct BigSpatialBundle<P: GridPrecision> {
     pub cell: GridCell<P>,
 }
 
-/// A [`SpatialBundle`] that also has a reference frame, allowing other high precision spatial
-/// bundles to be nested within that reference frame.
+/// A `SpatialBundle` that also has a reference frame, allowing other high precision spatial bundles
+/// to be nested within that reference frame.
 ///
-/// This is the floating origin equivalent of the [`SpatialBundle`].
+/// This is the floating origin equivalent of the `bevy` `SpatialBundle`.
 #[derive(Bundle, Default)]
 pub struct BigReferenceFrameBundle<P: GridPrecision> {
     /// The visibility of the entity.

src/floating_origins.rs

@@ -8,9 +8,9 @@ use bevy_utils::HashMap;
 
 /// Marks the entity to use as the floating origin.
 ///
-/// The [`GlobalTransform`] of all entities within this [`BigSpace`] will be computed relative to
-/// this floating origin. There should always be exactly one entity marked with this component
-/// within a [`BigSpace`].
+/// The [`GlobalTransform`](bevy_transform::components::GlobalTransform) of all entities within this
+/// [`BigSpace`] will be computed relative to this floating origin. There should always be exactly
+/// one entity marked with this component within a [`BigSpace`].
 #[derive(Component, Reflect)]
 pub struct FloatingOrigin;
 
@@ -23,8 +23,9 @@ pub struct FloatingOrigin;
 /// `ReferenceFrame`s, but only one `BigSpace`, at the root.
 ///
 /// Your world can have multiple [`BigSpace`]s, and they will remain completely independent. Each
-/// big space uses the floating origin contained within it to compute the [`GlobalTransform`] of all
-/// spatial entities within that `BigSpace`.
+/// big space uses the floating origin contained within it to compute the
+/// [`GlobalTransform`](bevy_transform::components::GlobalTransform) of all spatial entities within
+/// that `BigSpace`.
 #[derive(Debug, Default, Component, Reflect)]
 pub struct BigSpace {
     /// Set the entity to use as the floating origin within this high precision hierarchy.

src/lib.rs

@@ -1,5 +1,5 @@
-//! This [`bevy`] plugin makes it possible to build high-precision worlds that exceed the size of
-//! the observable universe, with no added dependencies, while remaining largely compatible with the
+//! This `bevy` plugin makes it possible to build high-precision worlds that exceed the size of the
+//! observable universe, with no added dependencies, while remaining largely compatible with the
 //! rest of the Bevy ecosystem.
 //!
 //! The next section explains the problem this solves in more detail, how this plugin works, and a
@@ -55,9 +55,9 @@
 //!   multiplayer - the server needs a source of truth for position that doesn't drift over time.
 //! - Virtually limitless volume and scale; you can work at the scale of subatomic particles, across
 //!   the width of the observable universe. Double precision is downright suffocating in comparison.
-//! - Uniform precision across the play area. Unlike double precision, the available precision
-//!   does not decrease as you move to the edge of the play area, it is instead relative to the
-//!   distance from the origin of the current grid cell.
+//! - Uniform precision across the play area. Unlike double precision, the available precision does
+//!   not decrease as you move to the edge of the play area, it is instead relative to the distance
+//!   from the origin of the current grid cell.
 //! - High precision coordinates are invisible if you don't need them. You can move objects using
 //!   their `Transform` alone, which results in decent ecosystem compatibility.
 //! - High precision is completely opt-in. If you don't add the `GridCell` component to an entity,

src/reference_frame/local_origin.rs

@@ -30,7 +30,7 @@ mod inner {
     /// An isometry that describes the location of the floating origin's grid cell's origin, in the
     /// local reference frame.
     ///
-    /// Used to compute the [`GlobalTransform`](bevy::transform::components::GlobalTransform) of
+    /// Used to compute the [`GlobalTransform`](bevy_transform::components::GlobalTransform) of
     /// every entity within a reference frame. Because this tells us where the floating origin cell
     /// is located in the local frame, we can compute the inverse transform once, then use it to
     /// transform every entity relative to the floating origin.