From df93e55d388748cac1ba4b99afac4125180f325a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Tue, 11 Jan 2022 02:59:48 -0300
Subject: [PATCH] Apply suggestions from code review

Co-authored-by: Schplee <24275329+Schplee@users.noreply.github.com>
---
 site/content/entry/yuzu-progress-report-dec-2021/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/content/entry/yuzu-progress-report-dec-2021/index.md b/site/content/entry/yuzu-progress-report-dec-2021/index.md
index df93f865..09f61a9c 100644
--- a/site/content/entry/yuzu-progress-report-dec-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-dec-2021/index.md
@@ -23,7 +23,7 @@ These are already available for both Mainline and [Early Access](https://yuzu-em
 
 The root of the problem in NVIDIA’s drivers seems to be in negation of integer and floating point values, and bitwise conversions of input values.
 
-On previous drivers you could assign a value to a variable named `x`, then assign `-x` as the value to a new variable named `y`. 
+On previous drivers, you could assign a value to a variable named `x`, then assign `-x` as the value to a new variable named `y`. 
 `y` would be equal to `-1 * x`.
 New drivers ignore this negation entirely, resulting in random spontaneous fires, security breaches, too many dogs causing a 
 [Howl](https://www.youtube.com/watch?v=Jw0c9z8EllE), and total chaos.