typos

Author: hg-anssi

src/en/devenv.md

@@ -115,15 +115,17 @@ $
 
 ### Rustc Tier guarantees
 
-As Rustc's backend is based on LLVM, it inherits and classifies its supported targets into tiers to communicate how much stability and testing each backend receives.
+As Rustc's backend is based on [LLVM], it inherits and classifies its supported targets into tiers to communicate how much stability and testing each backend receives.
+
+[LLVM]: https://llvm.org/
 
 #### Tier 1 - guaranteed to work
 
 The target is fully vetted by the community. It passes the entire test suite, receives regular regression testing, and is kept up‑to‑date with new releases. In practice, you can rely on consistent code generation, stable ABI, and predictable performance. Tier 1 targets can be thought of as "guaranteed to work".
 
 #### Tier 2 - guaranteed to build
 
-The target’s source code compiles cleanly, but it does not receive the same level of testing or maintenance as Tier 1. It may lack full coverage in the test suite, and certain optimizations or newer LLVM features could be missing or unstable. Users can still generate code for these backends, but they should expect occasional breakage or the need for manual patches. Tier 2 targets can be thought of as "guaranteed to build" but not as "guaranteed to work".
+The target’s source code compiles cleanly, but it does not receive the same level of testing or maintenance as Tier 1. It may lack full coverage in the test suite, and certain optimizations or newer [LLVM] features could be missing or unstable. Users can still generate code for these backends, but they should expect occasional breakage or the need for manual patches. Tier 2 targets can be thought of as "guaranteed to build" but not as "guaranteed to work".
 
 #### Tier 3
 

src/en/guarantees.md

@@ -51,7 +51,7 @@ The language paradigm is to ensure the absence of a UB in a program using only t
 
 Despite these memory safety guarantees, the language does not prevent
 
-* resource leaks (memory, IO, ...) (see the [memory management section](unsafe/memory.md#chapter-memory)),
+* resource leaks (memory, I/O, ...) (see the [memory management section](unsafe/memory.md#chapter-memory)),
 * numeric overflows (see the [integer operations section](integer.md#chapter-integer)).
 
 </div>

src/en/libraries.md

@@ -26,7 +26,9 @@ serde_json = "1.0.143"
 serde = "1.0.219"
 ```
 
-The default repository is [crates.io](https://crates.io). It is also possible to use [your own registry](https://doc.rust-lang.org/cargo/reference/registries.html).
+The default repository is [`crates.io`]. It is also possible to use [your own registry](https://doc.rust-lang.org/cargo/reference/registries.html).
+
+[`crates.io`]: https://crates.io
 
 ### Git Dependencies
 

src/en/unsafe/ffi.md

@@ -309,10 +309,12 @@ Safe Rust ensures that. Standard-compliant C and C++ compilers ensure that no
 value but 0 and 1 can be *stored* in a `_Bool`/`bool` value but cannot
 guarantee the absence of an *incorrect reinterpretation* (e.g., union types,
 pointer cast). To detect such a bad reinterpretation, sanitizers such as
-LLVM's `-fsanitize=bool` may be used.
+[LLVM]'s `-fsanitize=bool` may be used.
 
 </div>
 
+[LLVM]: https://llvm.org/
+
 #### References and pointers
 
 The types `&mut T` and `&T` are subject to the same validity requirements as the

src/fr/devenv.md

@@ -122,7 +122,9 @@ $
 
 ### Garantie de niveau pour Rustc
 
-Rustc utilise LLVM comme backend, il hérite donc du support de ce dernier et classe ses cibles prises en charge en différents niveaux afin d’indiquer le degré de stabilité et de tests effectué.
+Rustc utilise [LLVM] comme backend, il hérite donc du support de ce dernier et classe ses cibles prises en charge en différents niveaux afin d’indiquer le degré de stabilité et de tests effectué.
+
+[LLVM]: https://llvm.org/
 
 #### Tier 1 - Fonctionnement garanti
 

src/fr/guarantees.md

@@ -56,7 +56,7 @@ Le langage Rust est conçu dans le but de garantir l'absence d'*UB* dans un prog
 
 On notera que cette garantie qu'offre le langage Rust ***ne protège pas*** contre les erreurs suivantes :
 
-* fuites de resources (mémoire, IO, *etc.*) (voir la section sur la [gestion mémoire](unsafe/memory.md#chapter-memory)) ;
+* fuites de resources (mémoire, I/O, *etc.*) (voir la section sur la [gestion mémoire](unsafe/memory.md#chapter-memory)) ;
 * dépassements numériques (voir la section sur le traitement des [entiers](integer.md#chapter-integer)).
 
 </div>

src/fr/libraries.md

@@ -26,7 +26,9 @@ serde_json = "1.0.143"
 serde = "1.0.219"
 ```
 
-Le dépôt par défaut est [crates.io](https://crates.io). Il est aussi possible d'utiliser [son propre dépôt](https://doc.rust-lang.org/cargo/reference/registries.html).
+Le dépôt par défaut est [`crates.io`]. Il est aussi possible d'utiliser [son propre dépôt](https://doc.rust-lang.org/cargo/reference/registries.html).
+
+[`crates.io`]: https://crates.io
 
 ### Dépendances Git
 

src/fr/unsafe/ffi.md

@@ -329,10 +329,12 @@ compilateurs C et C++ assurent qu'aucune autre valeur que 0 et 1 ne peut être
 *stockée* dans un `_Bool`/`bool` mais ne peuvent garantir l'absence d'une
 *réinterprétation incorrecte* (par exemple dans un type union ou *via* un
 *cast* de pointeur). Pour détecter une telle réinterprétation, un
-*sanitizer* tel que l'option `-fsanitize=bool` de LLVM peut être utilisé.
+*sanitizer* tel que l'option `-fsanitize=bool` de [LLVM] peut être utilisé.
 
 </div>
 
+[LLVM]: https://llvm.org/
+
 #### Références et pointeurs
 
 Les types `&T` et `&mut T` imposent les mêmes contraintes de validité en mémoire