💡 Add Rust 2024

Author: dumindu

content/en/docs/a1.why-rust.md

@@ -4,11 +4,13 @@ slug: why-rust
 ---
 
 ## History of Rust
+
 Rust was initially designed and developed by former Mozilla employee **[Graydon Hoare](https://github.com/graydon)** as a personal project. Mozilla began sponsoring the project in 2009 and announced it in 2010. But the first stable release, Rust 1.0, was released on May 15, 2015.
 
-Since Rust 1.0, major updates have been released as [`Editions`](https://doc.rust-lang.org/stable/edition-guide/editions/) approximately every three years: Rust 2015 (with the release of Rust 1.0) , Rust 2018, Rust 2021, and Rust 2024, all maintaining backward compatibility.
+Since Rust 1.0, major updates have been released as [`Editions`](/docs/cargo-crates-and-basic-project-structure/#rust-editions) approximately every three years: Rust 2015 (with the release of Rust 1.0) , Rust 2018, Rust 2021, and Rust 2024, all maintaining backward compatibility.
 
 ## Initial Goals
+
 The goal of Rust is to be a good programming language for creating highly concurrent, safe and performant systems.
 
 > **"Rust is a systems programming language focused on three goals: safety, speed, and concurrency."
@@ -19,6 +21,7 @@ Rust is a very young and very modern language. It's a **[compiled programming la
 > One of Rust’s most unique and compelling features is [Ownership](/docs/ownership), which is used to achieve memory safety. Rust creates memory pointers optimistically, checks memory pointers’ limited accesses at compile-time with the usage of [References and Borrowing](/docs/borrowing). And it does automatic compile-time memory management by checking the [Lifetimes](/docs/lifetimes).
 
 ## Influences
+
 Its design elements came from a wide range of sources.
 
 - Abstract Machine Model: C
@@ -35,7 +38,6 @@ Its design elements came from a wide range of sources.
 
 and etc.
 
-
 Rust **doesn't use a built-in runtime** or an automated garbage collection system \(GC\).
 
 > 💡 However, async Rust requires an async runtime, which is provided by community-maintained crates like [`tokio`](https://github.com/tokio-rs/tokio), [`async-std`](https://github.com/async-rs/async-std), [`soml`](https://github.com/smol-rs/smol) etc. The async runtime will be bundled into the final executable.

content/en/docs/a4.cargo-crates-and-basic-project-structure.md

@@ -117,17 +117,15 @@ This is how [Cargo documentation describes](https://doc.rust-lang.org/cargo/guid
 
 ## Rust Editions
 
-The language has seen a series of improvements every three years through new editions since its initial stable release in 2015, including the initial version, **Rust 2015**, followed by **Rust 2018**, and the latest, **Rust 2021**.
+Rust guarantees backward compatibility while introducing major updates to the language. To support this, the `edition` field was added to the `Cargo.toml` file in Rust 2018, marking the first major update to the language ecosystem three years after its initial release. Editions are opt-in, meaning existing crates will not experience these changes until they explicitly migrate to the new edition.Rust guarantees backward compatibility between editions, allowing crates using older editions of Rust to interoperate seamlessly with those using newer versions.
 
-The `edition` key in the `Cargo.toml` file denotes the edition of the Rust compiler to be used for compiling the crate. Editions are opt-in, meaning existing crates will not see these changes until they explicitly migrate to the new edition. Rust guarantees backward compatibility between editions, allowing crates using older editions of Rust to interoperate seamlessly with those using newer versions.
-
-For new projects created by `cargo new`, it will set `edition = "2021"` by default in the `Cargo.toml` file. For example,
+For new projects created by `cargo new`, it will set `edition = "2024"` by default in the `Cargo.toml` file. For example,
 
 ```toml
 [package]
-name = "api"
+name = "hello_world"
 version = "0.1.0"
-edition = "2021"
+edition = "2024"
 ```
 
 ## 👨‍🏫 Before going to the next...