From 4cc4f09a6781e4c864023c33465e982d7ea78e8c Mon Sep 17 00:00:00 2001
From: Andrea Mazzoleni <amadvance@gmail.com>
Date: Mon, 11 Jan 2016 19:29:13 +0100
Subject: [PATCH] Auto update

---
 faq.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/faq.html b/faq.html
index 05c26824..38324318 100644
--- a/faq.html
+++ b/faq.html
@@ -143,7 +143,7 @@ Frequently Asked Questions for <span class="bold">SnapRAID</span>.
 <ul>
 <li><a href="#oomkiller">In Linux SnapRAID aborts without any error message</a></li>
 <li><a href="#pargrowerror">Running 'sync' I get the error 'Failed to grow parity file 'xxx' to size xxx due lack of space.'</a></li>
-<li><a href="#dupinode">I get the error 'Internal inode 'xxxxxx' incosistency...'</a></li>
+<li><a href="#dupinode">I get the error 'Internal inode xxx incosistency...'</a></li>
 </ul>
 
 
@@ -1174,7 +1174,7 @@ mkfs.ext4 -m 0 -T largefile4 DEVICE
 The '-T largefile4' and '-m 0' options should give more space available for the parity file.
 </p>
 
-<h3 id="dupinode">I get the error 'Internal inode 'xxxxxx' incosistency...'</h3>
+<h3 id="dupinode">I get the error 'Internal inode xxx incosistency...'</h3>
 <p>
 This means that SnapRAID found two different files using the same inode.
 This is theoretically something that should never happen,