Update 1.5 content based on 1.5 branch docs and new script's transform

Author: echeran

src/content/docs/1_5/tutorials/cargo.md

@@ -2,6 +2,8 @@
 title: Configuring Cargo.toml
 ---
 
+
+
 ICU4X makes heavy use of small crates and Cargo features in order to be highly modular. This tutorial is intended to help you set up a Cargo.toml file to download what you need for ICU4X.
 
 ## Basic Cargo.toml with compiled data
@@ -15,29 +17,33 @@ icu = "1.5"
 
 In your main.rs, you can use all stable ICU4X components for the recommended set of locales, which get compiled into the library.
 
+[« Fully Working Example »](https://github.com/unicode-org/icu4x/tree/release%2F1.5/tutorials/./crates/default)
 
 ## Cargo.toml with custom compiled data
 
 If you wish to use custom compiled data for ICU4X, no changes to Cargo.toml are required. Instead, set the `ICU4X_DATA_DIR` environment variable to the
 datagen output during your build:
 
 ```command
-icu4x-datagen --format baked --markers all --locales ru --out baked_data
+icu4x-datagen --format mod --keys all --locales ru --out baked_data
 ICU4X_DATA_DIR=$(pwd)/baked_data cargo build --release
 ```
 
+[« Fully Working Example »](https://github.com/unicode-org/icu4x/tree/release%2F1.5/tutorials/./crates/custom_compiled)
 
 ## Cargo.toml with experimental modules
 
 Experimental modules are published in a separate `icu_experimental` crate:
 
 ```toml
 [dependencies]
-icu = { version = "1.5", features = ["experimental"] }
+icu = "1.5"
+icu_experimental = "0"
 ```
 
 In your main.rs, you can now use e.g. the `icu_experimental::displaynames` module.
 
+[« Fully Working Example »](https://github.com/unicode-org/icu4x/tree/release%2F1.5/tutorials/./crates/experimental)
 
 ## Cargo.toml with Buffer Provider
 
@@ -49,8 +55,9 @@ icu = { version = "1.5", features = ["serde"] }
 icu_provider_blob = "1.5"
 ```
 
-To learn about building ICU4X data, including whether to check in the data blob file to your repository, see [Data management](/icu4x-docs/1_5/tutorials/data-management).
+To learn about building ICU4X data, including whether to check in the data blob file to your repository, see [data-management.md](/icu4x-docs/1_5/tutorials/./data-management).
 
+[« Fully Working Example »](https://github.com/unicode-org/icu4x/tree/release%2F1.5/tutorials/./crates/buffer)
 
 ## Cargo.toml with `Sync`
 
@@ -63,6 +70,7 @@ icu = { version = "1.5", features = ["sync"] }
 
 You can now use most ICU4X types when `Send + Sync` are required, such as when sharing across threads.
 
+[« Fully Working Example »](https://github.com/unicode-org/icu4x/tree/release%2F1.5/tutorials/./crates/sync)
 
 ## Cargo.toml with `build.rs` data generation
 
@@ -72,20 +80,20 @@ If you wish to use data generation in a `build.rs` script, you need to manually
 [dependencies]
 icu = { version = "1.5", default-features = false } # turn off compiled_data
 icu_provider = "1.5" # for databake
-icu_provider_baked = "1.5" # for databake
 zerovec = "0.9" # for databake
 
 # for build.rs:
 [build-dependencies]
 icu = "1.5"
-icu_provider_export = "1.5"
-icu_provider_source = "1.5"
+icu_datagen = "1.5"
 ```
 
-This example has an additional section for auto-generating the data in build.rs. In your build.rs, invoke the ICU4X Datagen API with the set of markers you require. Don't worry; if using databake, you will get a compiler error if you don't specify enough markers.
+This example has an additional section for auto-generating the data in build.rs. In your build.rs, invoke the ICU4X Datagen API with the set of keys you require. Don't worry; if using databake, you will get a compiler error if you don't specify enough keys.
 
 The build.rs approach has several downsides and should only be used if Cargo is the only build system you can use, and you cannot check in your data:
-* The build script with the whole of `icu_provider_source` in it is slow to build
-* If you're using networking features of `icu_provider_source` (behind the `networking` Cargo feature), the build script will access the network
-* Using the data requires ICU4X's [`_unstable`](https://docs.rs/icu_provider/latest/icu_provider/constructors/index.html) APIs with a custom data provider, and that `icu_provider_source` is the same *minor* version as the `icu` crate.
+* The build script with the whole of `icu_datagen` in it is slow to build
+* If you're using networking features of `icu_datagen` (behind the `networking` Cargo feature), the build script will access the network
+* Using the data requires ICU4X's [`_unstable`](https://docs.rs/icu_provider/latest/icu_provider/constructors/index.html) APIs with a custom data provider, and that `icu_datagen` is the same *minor* version as the `icu` crate.
 * `build.rs` output is not written to the console so it will appear that the build is hanging
+
+[« Fully Working Example »](https://github.com/unicode-org/icu4x/tree/release%2F1.5/tutorials/./crates/baked)