From d5e8a199f4b10e49660d95f1be254bd1410eaed7 Mon Sep 17 00:00:00 2001 From: Tim Siegel Date: Wed, 13 Dec 2023 14:02:54 -0500 Subject: [PATCH] [doc] Fix typo in CONTRIBUTING.md (#10971) # Objective Issue: There's a mistake in `CONTRIBUTING.md` ## Solution Use the correct word in the sentence. --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d2130b9f68..712ca05c36 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -50,7 +50,7 @@ Bevy is a completely free and open source game engine built in Rust. It currentl Bevy also currently has the following "development process" goals: * **Rapid experimentation over API stability**: We need the freedom to experiment and iterate in order to build the best engine we can. This will change over time as APIs prove their staying power. -* **Consistent vision**: The engine needs to feel consistent and cohesive. This takes precedent over democratic and/or decentralized processes. See our [*Bevy Organization doc*](/docs/the_bevy_organization.md) for more details. +* **Consistent vision**: The engine needs to feel consistent and cohesive. This takes precedence over democratic and/or decentralized processes. See our [*Bevy Organization doc*](/docs/the_bevy_organization.md) for more details. * **Flexibility over bureaucracy**: Developers should feel productive and unencumbered by development processes. * **Focus**: The Bevy Org should focus on building a small number of features excellently over merging every new community-contributed feature quickly. Sometimes this means pull requests will sit unmerged for a long time. This is the price of focus and we are willing to pay it. Fortunately Bevy is modular to its core. 3rd party plugins are a great way to work around this policy. * **User-facing API ergonomics come first**: Solid user experience should receive significant focus and investment. It should rarely be compromised in the interest of internal implementation details.