diff --git a/site/content/entry/yuzu-progress-report-may-2023/index.md b/site/content/entry/yuzu-progress-report-may-2023/index.md
index b0412fb3..b2e850e9 100644
--- a/site/content/entry/yuzu-progress-report-may-2023/index.md
+++ b/site/content/entry/yuzu-progress-report-may-2023/index.md
@@ -793,10 +793,11 @@ After the… peculiar [discussion](https://github.com/IGCIT/Intel-GPU-Community-
 We strongly recommend Intel Windows users to update to this driver to improve stability with most games.
 
 Sadly, fixing this issue showed us two areas where yuzu is at fault. 
-But luckily both issues have fixes in testing in the, at the time of writing, latest Early Access release. If everythin goes according to plan, they should hit Mainline in a few days. Stay tuned.
+But luckily, both issues have fixes in testing in the, at the time of writing, latest Early Access release. If everything goes according to plan, they should hit Mainline in a few days. Stay tuned.
 
-First problem is in yuzu's code. Some compute shaders have barriers in places that result in generating invalid SPIR-V code, and while NVIDIA and AMD have no problem with it, Intel is following the Vulkan specification much more closely and doesn’t like the result, leading to crashes.
-While we work on a solution, for now we recommend Intel users to keep the {{< gh-hovercard "10181" "freshly added" >}} “Enable Compute Pipelines (Intel Vulkan only)” disabled in `Emulation > Configure… > Graphics > Advanced` until we fix the affected shaders.
+First problem is in yuzu's code. 
+Some compute shaders have barriers in places that result in generating invalid SPIR-V code, and while NVIDIA and AMD have no problem with it, Intel is following the Vulkan specification much more closely and doesn’t like the result, leading to crashes.
+While we test the solution, for now we recommend Mainline Intel users to keep the {{< gh-hovercard "10181" "freshly added" >}} “Enable Compute Pipelines (Intel Vulkan only)” disabled in `Emulation > Configure… > Graphics > Advanced`.
 
 {{< imgs
 	"./compute.png| This is just temporary (famous last words…)"
@@ -804,9 +805,9 @@ While we work on a solution, for now we recommend Intel users to keep the {{< gh
 
 The other issue is a hardware limitation.
 Intel decided to remove support for Float64 operations on their Generation 12 graphics products (UHD 700/Xe/Arc) without providing a driver fallback.
-Well, it turns out that, for some reason, `Tears of the Kingdom` requires over the top precision in its cutscenes — precision that current Intel hardware physically lacks, causing crashes.
-We’re working on a Float64 to Float32 shader conversion to solve the problem.
-But for now, Intel users will have to get a save past the intro cutscene, or use OpenGL, as the OpenGL spec dictates that Float64 must be supported one way or another, even if it is via software emulation.
+Well, it turns out that, for some Goddess forsaken reason, `Tears of the Kingdom` requires over the top precision in its cutscenes — precision that current Intel hardware physically lacks, causing crashes.
+We’re testing a Float64 to Float32 shader conversion to solve the problem.
+For now, Mainline Intel users will have to get a save past the intro cutscene, or use OpenGL, as the OpenGL spec dictates that Float64 must be supported one way or another, even if it is via software emulation.
 
 ## Future projects