Added bscript thing

docs/blastproof/bootprocess.md

@@ -28,5 +28,5 @@ Blastproof boot process follow a very rigid sequences of steps that are detaille
   - Generating Shelter boot configuration
   - Allocating pages for kernel sections
   - Creating page table
-  - Parsing EFI Memory Map and transforming it into a understandable format for Vystem
+  - Parsing EFI Memory Map and transforming it into a understandable format for Vystem B
   - Jumping to kernel

docs/blastproof/fbm.md

@@ -13,7 +13,7 @@ Each FBM font start with the following 10 bytes header:
 - Width: 1 byte, the width in pixel of a glyph
 - Height: 1 byte, the heigth in pixel of a glyph
 
-Please note that the provided font in Vystem are only tested for ASCII encoding.
+Please note that the provided font in Vystem B are only tested for ASCII encoding.
 
 ## Glyphs table
 
@@ -50,4 +50,4 @@ When rendering the font, the renderer will take two values: background color and
 
 ## Provided font
 
-Vystem provides a basic font named `bitra`, with 12 pixels as width and 20 as height, only supporting ASCII characters. This font is stored in the file `FONT.FBM`.
+Vystem B provides a basic font named `bitra`, with 12 pixels as width and 20 as height, only supporting ASCII characters. This font is stored in the file `FONT.FBM`.

docs/blastproof/fs.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-Vystem define two new filesystems: InitFS and SignSyst. The purpose of these filesystems are to store any sensitive systems files. Both of these filesystems are designed to be integrated together. For each InitFS, there is always a SignSyst and vice versa. These filesystems are generated by the `initfsgen` utility. In this file, we describe how they are structured, not how they are generated, verified or used. Please take note that these filesystems has been designed for the x86-64 architecture and for little endian usage.
+Vystem B define two new filesystems: InitFS and SignSyst. The purpose of these filesystems are to store any sensitive systems files. Both of these filesystems are designed to be integrated together. For each InitFS, there is always a SignSyst and vice versa. These filesystems are generated by the `initfsgen` utility. In this file, we describe how they are structured, not how they are generated, verified or used. Please take note that these filesystems has been designed for the x86-64 architecture and for little endian usage.
 
 ## InitFS
 

docs/blastproof/index.md

@@ -2,11 +2,11 @@
 
 ## Introduction
 
-Blastproof is Vystem's bootloader. It is a UEFI x86-64 only bootloader that rely on EDK II for all hardware interactions. It is able to confirm the integrity of his files and partition, locate the kernel and load it into memory, using the specific boot protocol designed for Shelter.
+Blastproof is Vystem B's bootloader. It is a UEFI x86-64 only bootloader that rely on EDK II for all hardware interactions. It is able to confirm the integrity of his files and partition, locate the kernel and load it into memory, using the specific boot protocol designed for Shelter.
 
 ## Blastproof architectural overview
 
-The Blastproof bootloader rely mainly on the EDK II framework for printing to the EFI console, interacting with disks and FAT32 filesystem, graphic output protocol, and memory allocation. However, it uses Vystem standard formats for fonts, filesystems, security and integrity checks, graphic renderer, and kernel loading.
+The Blastproof bootloader rely mainly on the EDK II framework for printing to the EFI console, interacting with disks and FAT32 filesystem, graphic output protocol, and memory allocation. However, it uses Vystem B standard formats for fonts, filesystems, security and integrity checks, graphic renderer, and kernel loading.
 
 ## Ressources
 
@@ -14,7 +14,7 @@ The Blastproof bootloader rely mainly on the EDK II framework for printing to th
 2) [Keyboard layouts](kbdlayout.md)
 2) [Boot configuration](bootconfig.md)
 3) [Security and integrity model at boot level](security.md)
-4) [Vystem FAT Trusted Manifest](vftm.md)
+4) [Vystem B FAT Trusted Manifest](vftm.md)
 5) [Secure Boot Files Integrity Enforcement (SBFIE)](sbfie.md)
 6) [Custom filesystems](fs.md)
 7) [Font Bitmap](fbm.md)

docs/blastproof/vftm.md

@@ -1,8 +1,8 @@
-# Vystem FAT Trusted Manifest
+# Vystem B FAT Trusted Manifest
 
 ## Introduction
 
-Vystem FAT Trusted Manifest (VFTM) is a structure that can be found in the reserved sectors of any FAT32 filesystem generated by VyBuild (please see the conditions for VyBuild to generate this manifest in the VyBuild documentation). It's the first layer of defense in the Vystem Secure Boot Chain, being verified independantly at each boot.
+Vystem B FAT Trusted Manifest (VFTM) is a structure that can be found in the reserved sectors of any FAT32 filesystem generated by VyBuild (please see the conditions for VyBuild to generate this manifest in the VyBuild documentation). It's the first layer of defense in the Vystem B Secure Boot Chain, being verified independantly at each boot.
 
 ## Position and structure
 
@@ -34,7 +34,7 @@ VyBuild will sign the generated manifest with `sk_manifest`, and erase it immedi
 The manifest structure can be represented like this:
 ``` C
 #pragma pack(1)
-struct vystem_fat_trusted_manifest {
+struct vystem_b_fat_trusted_manifest {
   uint8_t sig[8];
   uint16_t manifest_version;
   uint16_t bootloader_version;