run prettier

Author: wprzytula

content/lessons/01_introduction/a_taste_of_rust-introductory_slides/A_taste_of_Rust.html

@@ -122,7 +122,7 @@ fn div(dividend: i32, divisor: NonZeroI32) -> i32 {
 }
 fn main() {
     // let quotient = div(2137, 42); // This would not type check, because 42 is not NonZeroI32.
-    
+
     // We have to create a NonZeroI32 instance:
     let non_zero_divisor_opt: Option<NonZeroI32> = NonZeroI32::new(42);
 
@@ -143,13 +143,14 @@ fn main() {
 
 ### But wait, we ended up with an `unwrap()` anyway. Did we then improve at all?
 
-Actually, yes. Now, the function (here: `div()`) with some (possibly complex) logic **only accepts** (so that the compiler verifies that in compile-time) valid arguments. This way, the function's code can be simpler (no invalid-input-related error handling). Also, it's easier to convince yourself that your number is nonzero that to make sure that it upholds all guarantees required in the docs of the function containing logic. 
+Actually, yes. Now, the function (here: `div()`) with some (possibly complex) logic **only accepts** (so that the compiler verifies that in compile-time) valid arguments. This way, the function's code can be simpler (no invalid-input-related error handling). Also, it's easier to convince yourself that your number is nonzero that to make sure that it upholds all guarantees required in the docs of the function containing logic.
 
 ---
 
 ## To `panic` or not to `panic`
 
 Don't panic:
+
 - if the failure is caused by bad user input - you don't want to open up a highway for DoS attackers, do you?
 - if the failure only affects some task and not the program in general, e.g. when the server returned bad data for a request of one of the users; others are unaffected;
 - if the failure is recoverable (there is a reasonable action to be done in such situation, e.g. give user the default value when the server can't be queried for the actual value);
@@ -159,7 +160,8 @@ Don't panic:
 ## To `panic` or not to `panic`
 
 Do panic:
+
 - if the failure is for sure caused by a bug in your code. It makes sense to inform the whole world that you wrote deficient software, by yelling at them. More seriously, this shortens the feedback loop and bugs are fixed earlier, instead of silently damaging production;
-- if the failure is not recoverable (there is no hope, the program is broken, *R.I.P.*, only the famous *restart* could help here);
+- if the failure is not recoverable (there is no hope, the program is broken, _R.I.P._, only the famous _restart_ could help here);
 
----
+---

content/lessons/02_ownership/dont_panic/dont_panic.html

@@ -359,4 +359,4 @@ fn main() {
 
 [ordering in Van Binh](https://classroom.github.com/a/prGDl5Xa)
 
-Deadline: 16.10.2024 23:59
+Deadline: 16.10.2024 23:59

content/lessons/02_ownership/dont_panic/dont_panic.md

@@ -47,7 +47,7 @@ fn agriculture() {
         "Nothing is better than {0} {2}, except for {1} {2},",
         num_animals, num_animals + 1, animal_name
     );
-    
+
     // Minimal assert.
     assert!(num_animals >= 42);
     // assert with a custom panic message.
@@ -83,6 +83,7 @@ fn agriculture() {
     // ]
 }
 ```
+
 ---
 
 ### Various ways to panic
@@ -91,10 +92,10 @@ fn agriculture() {
 fn panicking_is_fun() {
     panic!("A general panic.");
     assert!(false, "An assertion failed.");
-    
+
     unimplemented!("This code is not implemented.");
     todo!("This code is not YET implemented - it's going to change.");
-    
+
     unreachable!("We should never reach this line of code!");
 }
 ```
@@ -147,4 +148,4 @@ fn agriculture() {
 }
 ```
 
----
+---

content/lessons/02_ownership/index.md

@@ -109,4 +109,4 @@ So how do we handle situations which can fail? That's where the `Result` type co
 
 [Communications](https://classroom.github.com/a/gDraT0lo)
 
-Deadline: 23.10.2024 23:59
+Deadline: 23.10.2024 23:59

content/lessons/02_ownership/string_formatting/string_formatting.html

@@ -52,31 +52,32 @@ my-project
 
 ---
 
-## *Lib crates* can be shared
+## _Lib crates_ can be shared
 
-- *crates.io* is the main crate repository.
-- If you specify a dependency in `Cargo.toml`, it's fetched from `crates.io` automatically by *Cargo*.
-- `lib.rs` is the root of a *lib crate*.
+- _crates.io_ is the main crate repository.
+- If you specify a dependency in `Cargo.toml`, it's fetched from `crates.io` automatically by _Cargo_.
+- `lib.rs` is the root of a _lib crate_.
 
 ---
 
-## *Binary crates* can be executed
+## _Binary crates_ can be executed
 
 - `cargo run` executes the bin crate in your package.
 - If you have multiple bin crates, you have to specify which to run:
-`cargo run --bin <bin_name>`
+  `cargo run --bin <bin_name>`
 - Each bin crate in a package can import code from the lib crate there.
 
 ---
 
 ## Modules: grouping related code (& encapsulation)
+
 ```rust
 mod front_of_house {
     mod hosting {
         fn add_to_waitlist() {}
         fn seat_at_table() {}
     }
-    
+
     // Alternatively, this could be located in `serving.rs` file and imported.
     mod serving {
         fn take_order() {}
@@ -87,6 +88,7 @@ mod front_of_house {
 ```
 
 ---
+
 ## Modules: grouping related code (& encapsulation)
 
 ```
@@ -105,7 +107,8 @@ crate
 
 ## Exports & imports
 
-- exports: using privacy modifier (`pub`, `pub(crate)`, <no modifier>)
+- exports: using privacy modifier (`pub`, `pub(crate)`, [no modifier])
+
 ```rust
 mod some_mod {
     struct ModulePublic;
@@ -114,8 +117,10 @@ mod some_mod {
     pub struct WorldPublic;
 }
 ```
+
 - imports: using `use` statement
+
 ```rust
 use some_mod::CratePublic;
 pub use some_mod::WorldPublic; // <-- re-export
-```
+```