[Groonga-commit] groonga/groonga.org at 12bf11c [gh-pages] blog en: fix some typos

Back to archive index

Kentaro Hayashi null+****@clear*****
Fri Oct 28 17:01:32 JST 2016


Kentaro Hayashi	2016-10-28 17:01:32 +0900 (Fri, 28 Oct 2016)

  New Revision: 12bf11caf9924e4d54d1ed5798e93e1d4944bf5b
  https://github.com/groonga/groonga.org/commit/12bf11caf9924e4d54d1ed5798e93e1d4944bf5b

  Message:
    blog en: fix some typos
    
    changin ->
    changing
    
    difinitions ->
    definitions
    
    eariler ->
    earlier
    
    Fot ->
    For
    
    comsumption ->
    consumption

  Modified files:
    en/_posts/2016-10-29-groonga-6.1.0.md

  Modified: en/_posts/2016-10-29-groonga-6.1.0.md (+5 -5)
===================================================================
--- en/_posts/2016-10-29-groonga-6.1.0.md    2016-10-28 16:56:33 +0900 (e5a6b12)
+++ en/_posts/2016-10-29-groonga-6.1.0.md    2016-10-28 17:01:32 +0900 (8a64549)
@@ -22,13 +22,13 @@ Here are important changes in this release:
 
 #### Supported to sort load table names by key instead of ID to make output stable
 
-Before this release, dump command result of tables had been sorted by ID. Thus, when changin schema by adding and removing tables, it sometimes happens that a result of dumping database differs from without changing schema database. (Even if both of final difinitions are same.) This is not preferable behavior to compare dumping results.
+Before this release, dump command result of tables had been sorted by ID. Thus, when changing schema by adding and removing tables, it sometimes happens that a result of dumping database differs from without changing schema database. (Even if both of final definitions are same.) This is not preferable behavior to compare dumping results.
 
 Then, in this release, dumping results are output to be sorted by table name. When they contain reference type columns, it will be taken into consideration. This is incompatible change but it makes easy to compare result of dump command.
 
 #### Added document about index columns
 
-In this release, documents added about small/medium index columns. This feature had been implemented in eariler version, but it had been missing its concrete usage document.
+In this release, documents added about small/medium index columns. This feature had been implemented in earlier version, but it had been missing its concrete usage document.
 
 Then, in this time, we describe its usage. This method can apply indexing target to be reasonably small within data saved in database. If you make a good use of this feature, it makes reducing memory usage. There are two ways to use it.
 
@@ -36,16 +36,16 @@ Then, in this time, we describe its usage. This method can apply indexing target
 * medium index column
 
 Small index column can use when this column usage will not reach 1 billion records. It will reduce memory consumption by 1/256 compared with default index column's usage.
-Fot example, specify `COLUMN_INDEX|INDEX_SMALL` in `flags` parameter as follows:
+For example, specify `COLUMN_INDEX|INDEX_SMALL` in `flags` parameter as follows:
 
     column_create --table Ages --name people_age_small_index --flags COLUMN_INDEX|INDEX_SMALL --type People --source age
 
 It can apply when number of `People` table records is at most a few million.
 
 
-When using medium size index column, it can be made number of 1 billion records which contains a fixed size scalar column. It reduces memory comsumption by 5/24 compared with default index column's usage. There are some constraints to apply this type of column. In more detail, please refer to the [Create a medium index column](/docs/reference/commands/column_create.html#create-a-medium-index-column) section.
+When using medium size index column, it can be made number of 1 billion records which contains a fixed size scalar column. It reduces memory consumption by 5/24 compared with default index column's usage. There are some constraints to apply this type of column. In more detail, please refer to the [Create a medium index column](/docs/reference/commands/column_create.html#create-a-medium-index-column) section.
 
-Fot example, specify `COLUMN_INDEX|INDEX_MEDIUM` in `flags` parameter as follows:
+For example, specify `COLUMN_INDEX|INDEX_MEDIUM` in `flags` parameter as follows:
 
     column_create --table Ages --name people_age_medium_index --flags COLUMN_INDEX|INDEX_MEDIUM --type People --source age
 
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Back to archive index