update README.md to make it more funny

Author: Creative0708

README.md

@@ -15,13 +15,30 @@
 
 **cve-rs** allows you to introduce common memory vulnerabilities (such as buffer overflows and segfaults) into your Rust program in a memory safe manner.
 
-Rust is an amazing language. You can program a lot of useful things while ensuring that your program will stay safe. Unfortunately, safe Rust is quite limiting. For example, you cannot introduce code that could corrupt the program's memory. Now, with **cve-rs**, you can corrupt your program's memory without corrupting your program's memory.
+## Why choose **cve-rs**?
+- 🩸 Bleeding edge technology
+- 🕹️ Paradigm-changing (no more unsafe code!)
+- 🔥 Blazingly fast
+- 💡 Easy to use
+- Featuring way 👋 too 2️⃣ many 🤯 emojis in the 📖 readme 🔥 🦀 💨
+- **🦀 Built in 100% memory-safe Rust!**
+
+## Example
+```rs
+// With cve-rs, you can crash prod in a 🔥 blazingly fast manner!
+pub fn segfault() {
+	let null: &mut u8 = cve_rs::null_mut::<u8>();
+	*null = 42;
+}
+```
+
+![Segfault demo](/assets/segfault-demo.png)
 
-We are very committed to making sure **cve-rs** is memory-safe. We know that unsafe code can have unintended consequences, such as memory unsafety that causes programs to be insecure or unstable.
+Rust is an amazing language! You can program a lot of useful things while ensuring that your program will stay safe. Unfortunately, safe Rust is quite limiting. For example, you cannot introduce code that could corrupt the program's memory. Now, with **cve-rs**, **you can corrupt your program's memory without corrupting your program's memory!**
 
-That is why **cve-rs** uses `#![deny(unsafe_code)]` in the entire codebase. There is not a single block of `unsafe` code* in this project.
+We are very committed to making sure **cve-rs** is memory-safe. We know that unsafe code can have unintended consequences, such as memory unsafety that causes bugs like segmentation faults, use-after-frees, and buffer overflows!
 
-> *\* There is, unfortunately, one exception: In our tests, we compare the results of our safe `transmute` function against the regular `std::mem::transmute` function. Perhaps somewhat shortsightedly, the standard library implementation is unsafe. Regardless, this is only in our tests - the core library has no unsafe code.*
+That is why **cve-rs** uses `#![deny(unsafe_code)]` in the entire codebase. There is not a single block of `unsafe` code (except for some [tests](./src/transmute.rs#L56)) in this project.
 
 **cve-rs** implements the following bugs in safe Rust:
 
@@ -34,29 +51,26 @@ That is why **cve-rs** uses `#![deny(unsafe_code)]` in the entire codebase. Ther
 - `std::mem::transmute`
 - `std::ptr::null()`/`null_mut()` but for references
 
-Here is an example of usage with the `segfault` subcommand:
-
-![segfault demo](/assets/segfault-demo.png)
-
-## Install
+## Installation
 
 **cve-rs** can be used directly with Cargo.
 
 To use it as a library:
 
 ```sh
-cargo add cve-rs
+$ cargo add cve-rs
 ```
 
 Or to run our example binary:
 
 ```sh
-cargo install cve-rs
+$ cargo install cve-rs
+$ cve-rs
 ```
 
 ## WASM support
 
-**cve-rs** supports WASM through the WASI API.
+**cve-rs** supports WASM through the WASI API, and also to Webassembly that you can run in a browser!
 
 You can compile it and run it using [Wasmer](https://wasmer.io/) with the following commands:
 
@@ -65,9 +79,13 @@ cargo build --target wasm32-wasi
 wasmer run target/wasm32-wasi/debug/cve-rs.wasm
 ```
 
+## Wait, how safe is cve-rs?!?
+
+lmao
+
 ## Contributors
 
-Special thanks to [@Bright-Shard](https://github.com/Bright-Shard) and [@Creative0708](https://github.com/Creative0708)!
+Special thanks to [@Bright-Shard](https://github.com/Bright-Shard) and [@Creative0708](https://github.com/Creative0708), and everyone else that contributed to **cve-rs**!
 
 ## Can I use cve-rs in production?