Generated.

[homepage.git] / blog / archive / 2013 / 07 / index.html

diff --git a/blog/archive/2013/07/index.html b/blog/archive/2013/07/index.html
index 822e0426ee4e1b5465d360b80d6626cf14644e61..7b641b4a49794661d7306e0a899301d3cca5787b 100644 (file)
--- a/blog/archive/2013/07/index.html
+++ b/blog/archive/2013/07/index.html
@@ -122,11 +122,12 @@ have not yet had time to investigate those parts.</p>
 there.</p>
 
 <p>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.</p>
+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.</p>
 
       </div>
       <div class="tags">