clean up

bevyengine · Feb 8, 2023 · bdb5bad · bdb5bad
1 parent 33d6c76
commit bdb5bad
Showing 1 changed file with 4 additions and 5 deletions.
diff --git a/content/learn/book/migration-guides/0.9-0.10/_index.md b/content/learn/book/migration-guides/0.9-0.10/_index.md
@@ -632,11 +632,10 @@ The `FrameCount`  resource was previously only updated when using the `bevy_rend
 - Calls to `.label(MyLabel)` should be replaced with `.in_set(MySet)`
 - Stages have been removed. Replace these with system sets, and then add command flushes using the `apply_system_buffers` exclusive system where needed.
 - The `CoreStage`, `StartupStage,`RenderStage`and`AssetStage`enums have been replaced with`CoreSet`,`StartupSet, `RenderSet` and `AssetSet`. The same scheduling guarantees have been preserved.
-- Systems are no longer added to `CoreSet::Update` by default. Add systems manually if this behavior is needed, although you should consider adding your game logic systems to `CoreSchedule::FixedTimestep` instead for more reliable framerate-independent behavior.
-- Similarly, startup systems are no longer part of `StartupSet::Startup` by default. In most cases, this won’t matter to you.
-- For example, `add_system_to_stage(CoreStage::PostUpdate, my_system)` should be replaced with
-- `add_system(my_system.in_set(CoreSet::PostUpdate)`
-
+  - Systems are no longer added to `CoreSet::Update` by default. Add systems manually if this behavior is needed, although you should consider adding your game logic systems to `CoreSchedule::FixedTimestep` instead for more reliable framerate-independent behavior.
+  - Similarly, startup systems are no longer part of `StartupSet::Startup` by default. In most cases, this won’t matter to you.
+  - For example, `add_system_to_stage(CoreStage::PostUpdate, my_system)` should be replaced with
+  - `add_system(my_system.in_set(CoreSet::PostUpdate)`
 - When testing systems or otherwise running them in a headless fashion, simply construct and run a schedule using `Schedule::new()` and `World::run_schedule` rather than constructing stages
 - Run criteria have been renamed to run conditions. These can now be combined with each other and with states.
 - Looping run criteria and state stacks have been removed. Use an exclusive system that runs a schedule if you need this level of control over system control flow.