codespell: lint spelling

2 files changed, 9 insertions, 9 deletions

diff --git a/src/content/blog/linux/2024-year-of-the-linux-desktop.md b/src/content/blog/linux/2024-year-of-the-linux-desktop.md
index 42051bd..90b0f9d 100644
--- a/src/content/blog/linux/2024-year-of-the-linux-desktop.md
+++ b/src/content/blog/linux/2024-year-of-the-linux-desktop.md
@@ -27,7 +27,7 @@ A majority of applications these days are also just all running a glorified web
 # Gaming
 Gaming was also one of my major concerns when switching over. Maybe 2-3 years ago I would've been much more unwilling to switch, but these days gaming on Linux has taken off like a rocket ship thanks largely in part to Valve's adoption of Arch on the Steam Deck.
 
-As of writing this, 76% of the top 1000 games on Steam have achieved Platnium or Gold status in terms of compatability according to [ProtonDB](https://www.protondb.com/). Pretty much all the games I want to play on Steam are working very well if not better than if I had run them on Windows.
+As of writing this, 76% of the top 1000 games on Steam have achieved Platnium or Gold status in terms of compatibility according to [ProtonDB](https://www.protondb.com/). Pretty much all the games I want to play on Steam are working very well if not better than if I had run them on Windows.
 
 <img src="https://files.catbox.moe/6zqxhz.png">
 
diff --git a/src/content/blog/linux/kvm/kvm-part1.md b/src/content/blog/linux/kvm/kvm-part1.md
index 93a222c..b9d76e3 100644
--- a/src/content/blog/linux/kvm/kvm-part1.md
+++ b/src/content/blog/linux/kvm/kvm-part1.md
@@ -12,25 +12,25 @@ But before all that, Below are some of the other options that you may want to co
 ## Virtual Machine
 A good but generally resource intensive option since you're technically emulating an entire system. I won't get into this option since setting up a VM using something like Virtualbox or VMware is pretty standard.
 
-## Compatability Layers
-At a high level, compatability layers will map the "syscalls" from binaries of some other system to the native ones. This means that programs compiled for a different operating system will run just fine (assuming that all required calls have been handled). This means that its much less resource intensive than running a VM, since its more of a "handle the syscalls as its needed" basis.
+## Compatibility Layers
+At a high level, compatibility layers will map the "syscalls" from binaries of some other system to the native ones. This means that programs compiled for a different operating system will run just fine (assuming that all required calls have been handled). This means that its much less resource intensive than running a VM, since its more of a "handle the syscalls as its needed" basis.
 
-While compatability layers for Windows software, such as Wine, exist on Linux; these systems are far from being feature complete and often times do not replicate the experience perfectly. However, its always a good idea to check if your non-compatible software will run using this method since its probably both the easiest and the most convenient.
+While compatibility layers for Windows software, such as Wine, exist on Linux; these systems are far from being feature complete and often times do not replicate the experience perfectly. However, its always a good idea to check if your non-compatible software will run using this method since its probably both the easiest and the most convenient.
 
 ## Dual Boot
-Another option that many people opt for is to "dual boot", allocating room for 2 operating systems on the same machine. This will let you keep both operating systems seperate to an extent, while still maintaining a Windows system running on bare metal without any of the "funny business" above.
+Another option that many people opt for is to "dual boot", allocating room for 2 operating systems on the same machine. This will let you keep both operating systems separate to an extent, while still maintaining a Windows system running on bare metal without any of the "funny business" above.
 
 If you need to deal with thing such as game anti-cheats that dive deeply into the kernel level, this is probably the ideal method since you're pretty much just running an ordinary Windows machine.
 
-But paritioning and managing the storage for both Linux and Windows at the same time is quite annoying. Problems arise when trying to expand or shrink partitions. It can be a real pain to move partitions around to allow for expansion or shrinkage. Then on top of all that you run the risk of either system somehow destroying the boot process of the other (as commonly documented online).
+But partitioning and managing the storage for both Linux and Windows at the same time is quite annoying. Problems arise when trying to expand or shrink partitions. It can be a real pain to move partitions around to allow for expansion or shrinkage. Then on top of all that you run the risk of either system somehow destroying the boot process of the other (as commonly documented online).
 
 To simply put it, you miss out on the flexibility of the other two options above.
 
 # Kernel-based Virtual Machine (KVM)
-KVMs are a solution I've found that tackles pretty much all of the problems above. Since its a "type-1 hypervisor", all OS level components such as memory management or I/O is implemented as some Linux process. This means that all the resouces your Linux machine has will be made available to the VM and it'll be like you're running on bare-metal. This gets you performance that far surpasses a traditional type-2 VM, and it comes very close to what you would've gotten running on bare metal.
+KVMs are a solution I've found that tackles pretty much all of the problems above. Since its a "type-1 hypervisor", all OS level components such as memory management or I/O is implemented as some Linux process. This means that all the resources your Linux machine has will be made available to the VM and it'll be like you're running on bare-metal. This gets you performance that far surpasses a traditional type-2 VM, and it comes very close to what you would've gotten running on bare metal.
 
-Additionally, its flexible since you can store the VM's disk as a single qcow2 file (or allocate actual space on the SSD). Paritioning and resizing becomes much easier and you won't need to run the risk of accidentally wiping Windows' EFI partition.
+Additionally, its flexible since you can store the VM's disk as a single qcow2 file (or allocate actual space on the SSD). Partitioning and resizing becomes much easier and you won't need to run the risk of accidentally wiping Windows' EFI partition.
 
-Finally, it'll also get you the compatability that Wine lacks since you're running the actual OS.
+Finally, it'll also get you the compatibility that Wine lacks since you're running the actual OS.