diff options
| author | w96k <w96k@debian> | 2022-11-14 12:34:36 +0400 |
|---|---|---|
| committer | w96k <w96k@debian> | 2022-11-14 12:34:36 +0400 |
| commit | 197867debf421ef27760e6a61a7a3ce50b5bee79 (patch) | |
| tree | 1deadedca0ea8ac2fb0663408987a0346c2b028c | |
| parent | ebbbf4f590b4a8f643776081f8c48faf21024c8e (diff) | |
Fix typo
| -rw-r--r-- | content/en/posts/ram-fix.org | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/content/en/posts/ram-fix.org b/content/en/posts/ram-fix.org index 6e9649e..6ed06a0 100644 --- a/content/en/posts/ram-fix.org +++ b/content/en/posts/ram-fix.org @@ -5,10 +5,10 @@ * RAM failures: How to detect and fix #+BEGIN_abstract -If your system break in unexpected ways and you can't understand why it -might be the RAM issue. In this article, I will try to explain why RAM -is getting broken, how to detect it, and how to potentially fix it -without going too deep into details. +If your system breaks in unexpected ways and you can't understand why, +it might be the RAM issue. In this article, I will try to explain +without going too deep into details. why RAM is getting broken, how to +detect it, and how to fix it. #+END_abstract #+ATTR_HTML: :loading lazy |