From fb36cb723c00514029faa0911cd4b1a2fb4551f3 Mon Sep 17 00:00:00 2001 From: Petter Reinholdtsen Date: Wed, 17 Jul 2013 22:18:30 +0000 Subject: [PATCH] Typo. --- blog/data/2013-07-17-new-laptop.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/blog/data/2013-07-17-new-laptop.txt b/blog/data/2013-07-17-new-laptop.txt index ec1c216881..92d3d66bfe 100644 --- a/blog/data/2013-07-17-new-laptop.txt +++ b/blog/data/2013-07-17-new-laptop.txt @@ -95,8 +95,9 @@ have not yet had time to investigate those parts.

there.

As for the answer to the question in the title of this blog post, -as far as I know, the only solution is to replace the disk. It might -be possible to flash it with Intel firmware instead of the Lenovo -firmware. But I have not tried and did not want to do so without -approval from Lenovo as I wanted to keep the warranty on the disk -until a solution was found and they wanted the broken disks back.

+as far as I know, the only solution I know about is to replace the +disk. It might be possible to flash it with Intel firmware instead of +the Lenovo firmware. But I have not tried and did not want to do so +without approval from Lenovo as I wanted to keep the warranty on the +disk until a solution was found and they wanted the broken disks +back.

-- 2.47.2