WIP

README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/vojtechkral/cargo-fixture/actions/workflows/CI.yaml/badge.svg)](https://github.com/vojtechkral/cargo-fixture/actions/workflows/CI.yaml)
 [![crates](https://img.shields.io/crates/v/cargo-fixture.svg)](https://crates.io/crates/cargo-fixture)
-[![Documentation](https://docs.rs/cargo-fixture/badge.svg)](https://docs.rs/cargo-fixture)
+[![docs](https://docs.rs/cargo-fixture-lib/badge.svg)](https://docs.rs/cargo-fixture-lib)
 
 `cargo fixture` is a cargo extension that let's you surround `cargo test` invocations with arbitrary Rust setup and teardown code.
 It can be used to run network servers that tests connect to, spin up docker containers, prepare test data in cargo's tmpdir, check for presence of programs,... or really anything that can be done from Rust code. Any provided resources can be released after `cargo test` finishes, whether manually, using RAII guards or closures.

examples/docker/README.md

@@ -6,4 +6,4 @@ No that the container preparation may take some time upon first run as the image
 
 The [test code](./tests/test.rs) reads the variable and connects to the DB.
 
-Back in the fixture, after the tests are run, the dockertest run closure exists and the library stops and removes the docker container and network (if any).
+Back in the fixture after the tests are run, the dockertest the docker container is stopped and removed.