Update Docs CI with mdbook translation support (#516)

* Update Docs CI with mdbook translation support #514

* install mdbook with --rev

docs/guide/src/en/async/spawn.md

@@ -3,7 +3,7 @@
 The `use_future` and `use_coroutine` hooks are useful if you want to unconditionally spawn the future. Sometimes, though, you'll want to only spawn a future in response to an event, such as a mouse click. For example, suppose you need to send a request when the user clicks a "log in" button. For this, you can use `cx.spawn`:
 
 ```rust
-{{#include ../../examples/spawn.rs:spawn}}
+{{#include ../../../examples/spawn.rs:spawn}}
 ```
 
 > Note: `spawn` will always spawn a *new* future. You most likely don't want to call it on every render.
@@ -15,7 +15,7 @@ However, since you'll typically need a way to update the value of a hook, you ca
 To make this a bit less verbose, Dioxus exports the `to_owned!` macro which will create a binding as shown above, which can be quite helpful when dealing with many values.
 
 ```rust
-{{#include ../../examples/spawn.rs:to_owned_macro}}
+{{#include ../../../examples/spawn.rs:to_owned_macro}}
 ```
 
 Calling `spawn` will give you a `JoinHandle` which lets you cancel or pause the future.
@@ -25,5 +25,5 @@ Calling `spawn` will give you a `JoinHandle` which lets you cancel or pause the
 Sometimes, you might want to spawn a background task that needs multiple threads or talk to hardware that might block your app code. In these cases, we can directly spawn a Tokio task from our future. For Dioxus-Desktop, your task will be spawned onto Tokio's Multithreaded runtime:
 
 ```rust
-{{#include ../../examples/spawn.rs:tokio}}
+{{#include ../../../examples/spawn.rs:tokio}}
 ```