Fix: engine::new() visibility (#854)

* fix: engine `new` visibility

arbiter-engine/src/examples/timed_message/mod.rs

@@ -16,10 +16,6 @@ fn default_max_count() -> Option<u64> {
     Some(3)
 }
 
-fn default_max_count() -> Option<u64> {
-    Some(3)
-}
-
 #[derive(Debug, Clone, Serialize, Deserialize)]
 pub(crate) struct TimedMessage {
     delay: u64,

arbiter-engine/src/machine.rs

@@ -185,7 +185,7 @@ where
     E: DeserializeOwned + Send + Sync + 'static,
 {
     /// Creates a new [`Engine`] with the given [`Behavior`] and [`Receiver`].
-    pub(crate) fn new(behavior: B) -> Self {
+    pub fn new(behavior: B) -> Self {
         Self {
             behavior: Some(behavior),
             state: State::Uninitialized,

arbiter-macros/Cargo.toml

@@ -1,5 +1,6 @@
 [package]
 name = "arbiter-macros"
+version = "0.1.0"
 
 [lib]
 proc-macro = true

documentation/src/usage/arbiter_engine/index.md

@@ -3,7 +3,7 @@
 The goal of this crate is to abstract away the work required to set up agents, their behaviors, and the worlds they live in.
 At the moment, all interaction of agents is done through the `arbiter-core` crate and is meant to be for local simulations and it is not yet generalized for the case of live network automation.
 
-## Heirarchy
+## Hierarchy
 The primary components of `arbiter-engine` are, from the bottom up:
 - `Behavior<E>`: This is an event-driven behavior that takes in some item of type `E` and can act on that. 
 The `Behavior<E>` has two methods: `startup` and `process`. 

documentation/src/usage/arbiter_engine/worlds_and_universes.md

@@ -56,7 +56,7 @@ fn setup_world(id: &str) -> World {
     world.add_agent(agent);
 }
 
-fn main() {
+async fn run() {
     let world = setup_world("my_world");
     world.run().await;
 }
@@ -82,4 +82,4 @@ fn main() {
     universe.add_world(setup_world("my_other_world"));
     universe.run_worlds().await;
 }
-```
+```