Other CI fixes

Author: BigWingBeat

crates/bevy_camera/src/camera.rs

@@ -198,7 +198,7 @@ pub struct MainPassResolutionOverride(pub UVec2);
 ///            
 /// ```
 ///
-/// See the "camera_sub_view" example for more information.
+/// See the `camera_sub_view` example for more information.
 ///
 /// ## [`SubViewSourceProjection`]
 ///
@@ -402,7 +402,7 @@ pub enum ViewportConversionError {
     #[error("computed coordinate beyond `Camera`'s far plane")]
     PastFarPlane,
     /// The Normalized Device Coordinates could not be computed because the `camera_transform`, the
-    /// `world_position`, or the projection matrix defined by [`Projection`](super::projection::Projection)
+    /// `world_position`, or the projection matrix defined by [`Projection`]
     /// contained `NAN` (see [`world_to_ndc`][Camera::world_to_ndc] and [`ndc_to_world`][Camera::ndc_to_world]).
     #[error("found NaN while computing NDC")]
     InvalidData,
@@ -572,7 +572,7 @@ impl Camera {
             .map(|t: &RenderTargetInfo| t.scale_factor)
     }
 
-    /// The projection matrix computed using this camera's [`Projection`](super::projection::Projection).
+    /// The projection matrix computed using this camera's [`Projection`].
     #[inline]
     pub fn clip_from_view(&self) -> Mat4 {
         self.computed.clip_from_view
@@ -792,7 +792,7 @@ impl Camera {
     /// [`world_to_viewport`](Self::world_to_viewport).
     ///
     /// Returns `None` if the `camera_transform`, the `world_position`, or the projection matrix defined by
-    /// [`Projection`](super::projection::Projection) contain `NAN`.
+    /// [`Projection`] contain `NAN`.
     ///
     /// # Panics
     ///
@@ -818,7 +818,7 @@ impl Camera {
     /// [`world_to_viewport`](Self::world_to_viewport).
     ///
     /// Returns `None` if the `camera_transform`, the `world_position`, or the projection matrix defined by
-    /// [`Projection`](super::projection::Projection) contain `NAN`.
+    /// [`Projection`] contain `NAN`.
     ///
     /// # Panics
     ///

examples/README.md

@@ -164,6 +164,7 @@ Example | Description
 [Lighting](../examples/3d/lighting.rs) | Illustrates various lighting options in a simple scene
 [Lightmaps](../examples/3d/lightmaps.rs) | Rendering a scene with baked lightmaps
 [Lines](../examples/3d/lines.rs) | Create a custom material to draw 3d lines
+[Magnifier](../examples/usage/magnifier.rs) | Demonstrates magnifying part of the screen with CameraSubView
 [Manual Material Implementation](../examples/3d/manual_material.rs) | Demonstrates how to implement a material manually using the mid-level render APIs
 [Mesh Ray Cast](../examples/3d/mesh_ray_cast.rs) | Demonstrates ray casting with the `MeshRayCast` system parameter
 [Meshlet](../examples/3d/meshlet.rs) | Meshlet rendering for dense high-poly scenes (experimental)
@@ -594,7 +595,6 @@ Example | Description
 --- | ---
 [Context Menu](../examples/usage/context_menu.rs) | Example of a context menu
 [Cooldown](../examples/usage/cooldown.rs) | Example for cooldown on button clicks
-[Magnifier](../examples/usage/magnifier.rs) | Demonstrates magnifying part of the screen with CameraSubView
 
 ### Window
 

examples/usage/magnifier.rs

@@ -150,7 +150,7 @@ fn update_sub_view(
     let viewport_pos = cursor - viewport_half_size;
     viewport.physical_position = viewport_pos.as_uvec2();
 
-    // Normalise the position to the 0..1 range the sub view expects
+    // Normalize the position to the 0..1 range the sub view expects
     let mut offset = cursor / window_size;
 
     // A subview scale of 1.0 makes the full window image visible within the much smaller viewport (i.e. very "zoomed out").
@@ -166,7 +166,7 @@ fn update_sub_view(
     // is actually the projection of the other camera (that renders the background image).
     // This means we must ensure that at least one of the axes of the projections of both of these cameras is the same,
     // so that we get the correct result from specifying the fraction of the "full view" we want as the fraction that the sub view uses.
-    // Fortunately, this is already the case for us, as both projections were initialised with all the same default parameters,
+    // Fortunately, this is already the case for us, as both projections were initialized with all the same default parameters,
     // except the aspect ratio. The aspect ratio only affects the x axis, so we pick the y axis instead.
     let scale = size.y;