diff --git a/CHANGES.txt b/CHANGES.txt
index 26fd765fc9f..a851432b243 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -148,6 +148,7 @@ Release 0.91.0 - Unreleased
                coprocessor collection
    HBASE-3729  Get cells via shell with a time range predicate
                (Ted Yu via Stack)
+   HBASE-3764  Book.xml - adding 2 FAQs (SQL and arch question)
 
   TASK
    HBASE-3559  Move report of split to master OFF the heartbeat channel
diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml
index 444f2fa73ba..78c976b8742 100644
--- a/src/docbkx/book.xml
+++ b/src/docbkx/book.xml
@@ -1235,6 +1235,26 @@ false
                 </para>
             </answer>
         </qandaentry>
+        <qandaentry xml:id="faq.sql">
+            <question><para>Does HBase support SQL?</para></question>
+            <answer>
+                <para>
+                    Not really.  SQL-ish support for HBase via <link xlink:href="http://hive.apache.org/">Hive</link> is in development, however Hive is based on MapReduce which is not generally suitable for low-latency requests.
+                    See the <link linkend="datamodel">Data Model</link> section for examples on the HBase client.
+                </para>
+            </answer>
+        </qandaentry>
+        <qandaentry xml:id="faq.hdfs.hbase">
+            <question><para>How does HBase work on top of HDFS?</para></question>
+            <answer>
+                <para>
+                    <link xlink:href="http://hadoop.apache.org/hdfs/">HDFS</link> is a distributed file system that is well suited for the storage of large files.  It's documentation 
+                    states that it is not, however, a general purpose file system, and does not provide fast individual record lookups in files. 
+                    HBase, on the other hand, is built on top of HDFS and provides fast record lookups (and updates) for large tables.  This can sometimes be a point of conceptual confusion.
+                    See the <link linkend="datamodel">Data Model</link> and <link linkend="architecture">Architecture</link> sections for more information on how HBase achieves its goals.
+                </para>
+            </answer>
+        </qandaentry>
         <qandaentry xml:id="brand.new.compressor">
             <question><para>Why are logs flooded with '2011-01-10 12:40:48,407 INFO org.apache.hadoop.io.compress.CodecPool: Got
             brand-new compressor' messages?</para></question>