diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1eaea1d1..0888e945 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,8 +1,10 @@
 # Changelog
 
-## 0.8.2-dev
+## 0.8.2 July 2, 2020
  - `client.log_debug()` will write debug logs to file when specified with `--debug-log-file=`
  - add `-debug-log-format=` to switch between `json` (default) and `raw` formats
+ - cleanup code with clippy, automate clippy with PRs
+ - add optional compile-time `rustls` feature
 
 ## 0.8.1 June 30, 2020
  - sort stats by method:name to ease comparisons
diff --git a/Cargo.toml b/Cargo.toml
index 595b67bb..6cfae5f9 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "goose"
-version = "0.8.2-dev"
+version = "0.8.2"
 authors = ["Jeremy Andrews <jeremy@tag1consulting.com>"]
 edition = "2018"
 description = "A load testing tool inspired by Locust."
diff --git a/README.md b/README.md
index 4b9e33f9..56dab9dd 100644
--- a/README.md
+++ b/README.md
@@ -47,9 +47,9 @@ resulting binary only displays "Hello, world!":
 ```
 $ cargo run
     Updating crates.io index
-  Downloaded goose v0.8.1
+  Downloaded goose v0.8.2
       ...
-   Compiling goose v0.8.1
+   Compiling goose v0.8.2
    Compiling loadtest v0.1.0 (/home/jandrews/devel/rust/loadtest)
     Finished dev [unoptimized + debuginfo] target(s) in 52.97s
      Running `target/debug/loadtest`
@@ -165,7 +165,7 @@ load tests. For example, pass the `-h` flag to the `simple` example,
 `cargo run --example simple -- -h`:
 
 ```
-Goose 0.8.1
+Goose 0.8.2
 CLI options available when launching a Goose load test
 
 USAGE:
@@ -223,9 +223,9 @@ MiB Swap:  10237.0 total,  10234.7 free,      2.3 used.   8401.5 avail Mem
 Here's the output of running the loadtest. The `-v` flag sends `INFO` and more critical messages to stdout (in addition to the log file). The `-u1024` tells Goose to spin up 1,024 users. The `-r32` option tells Goose to spin up 32 users per second. The `-t 10m` option tells Goose to run the load test for 10 minutes, or 600 seconds. The `--print-stats` flag tells Goose to collect statistics during the load test, and the `--status-codes` flag tells it to include statistics about HTTP Status codes returned by the server. Finally, the `--only-summary` flag tells Goose to only display the statistics when the load test finishes, otherwise it would display running statistics every 15 seconds for the duration of the test.
 
 ```
-$ cargo run --release --example simple -- --host http://apache.fosciana -v -c1024 -r32 -t 10m --print-stats --status-codes --only-summary
+$ cargo run --release --example simple -- --host http://apache.fosciana -v -u1024 -r32 -t 10m --print-stats --status-codes --only-summary
     Finished release [optimized] target(s) in 0.05s
-     Running `target/release/examples/simple --host 'http://apache.fosciana' -v -c1024 -r32 -t 10m --print-stats --status-codes --only-summary`
+     Running `target/release/examples/simple --host 'http://apache.fosciana' -v -u1024 -r32 -t 10m --print-stats --status-codes --only-summary`
 18:42:48 [ INFO] Output verbosity level: INFO
 18:42:48 [ INFO] Logfile verbosity level: INFO
 18:42:48 [ INFO] Writing to log file: goose.log
diff --git a/src/goose.rs b/src/goose.rs
index dc87186f..20c9e0dc 100644
--- a/src/goose.rs
+++ b/src/goose.rs
@@ -1502,7 +1502,7 @@ impl GooseUser {
     ///
     /// By default, Goose configures two options when building a Reqwest client. The first
     /// configures Goose to report itself as the user agent requesting web pages (ie
-    /// `goose/0.8.0`). The second option configures Reqwest to store cookies, which is
+    /// `goose/0.8.2`). The second option configures Reqwest to store cookies, which is
     /// generally necessary if you aim to simulate logged in users.
     ///
     /// # Default configuration: