[jira] [Resolved] (HBASE-6264) Typos in the book documentation

["stack (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-6264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-6264.
--------------------------

       Resolution: Fixed
    Fix Version/s: 0.96.0
     Hadoop Flags: Reviewed

I made Jean-Marc's suggested changes.  They'll show on site next time we push it up.
                
> Typos in the book documentation
> -------------------------------
>
>                 Key: HBASE-6264
>                 URL: https://issues.apache.org/jira/browse/HBASE-6264
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.94.0
>            Reporter: Jean-Marc Spaggiari
>            Priority: Minor
>              Labels: documentation
>             Fix For: 0.96.0
>
>         Attachments: typo_HBASE_6264.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> In section 6.9: http://hbase.apache.org/book/secondary.indexes.html
> In section 9.2: http://hbase.apache.org/book/arch.catalog.html
> There is "are are" twice. I'm not 100% sure what's the best way to propose a fix, so I have included the patch below. If that's fine, I will probably propose some other corrections.
> JM
> Index: branches/0.94/src/docbkx/book.xml
> ===================================================================
> --- branches/0.94/src/docbkx/book.xml	(révision 1352979)
> +++ branches/0.94/src/docbkx/book.xml	(copie de travail)
> @@ -828,7 +828,7 @@
>    Secondary Indexes and Alternate Query Paths
>    </title>
>    <para>This section could also be titled "what if my table rowkey looks like <emphasis>this</emphasis> but I also want to query my table like <emphasis>that</emphasis>."
> -  A common example on the dist-list is where a row-key is of the format "user-timestamp" but there are are reporting requirements on activity across users for certain 
> +  A common example on the dist-list is where a row-key is of the format "user-timestamp" but there are reporting requirements on activity across users for certain 
>    time ranges.  Thus, selecting by user is easy because it is in the lead position of the key, but time is not.
>    </para>
>    <para>There is no single answer on the best way to handle this because it depends on...
> @@ -1324,7 +1324,7 @@
>  
>  	<section xml:id="arch.catalog">
>  	 <title>Catalog Tables</title>
> -	  <para>The catalog tables -ROOT- and .META. exist as HBase tables.  They are are filtered out 
> +	  <para>The catalog tables -ROOT- and .META. exist as HBase tables.  They are filtered out 
>  	  of the HBase shell's <code>list</code> command, but they are in fact tables just like any other.
>       </para>
>  	  <section xml:id="arch.catalog.root">

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira