rroonga 5.0.4-x86-mingw32 → 5.0.5-x86-mingw32

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/indexing.txt

@@ -61,7 +61,7 @@ We define a schema:
 .. include:: ../example/reference/indexing-schema.log
 .. table_create Tweets TABLE_NO_KEY
 .. column_create Tweets content COLUMN_SCALAR ShortText
-.. table_create Lexicon TABLE_HASH_KEY|KEY_NORMALIZE ShortText --default_tokenizer TokenBigram
+.. table_create Lexicon TABLE_HASH_KEY ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
 
 We register data:
 
@@ -74,7 +74,7 @@ We register data:
 .. {"content":"I'm sleepy... Have a nice day... Good night..."}
 .. ]
 
-We search without index. We get no result:
+We can search with sequential search when we don't have index:
 
 .. groonga-command
 .. include:: ../example/reference/indexing-search-without-index.log

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/query_expanders/tsv.txt

@@ -150,4 +150,4 @@ loaded only at the plugin load time.
 See also
 --------
 
-  * :ref:`query-expansion`
+  * :ref:`select-query-expansion`

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/regular_expression.txt

@@ -39,6 +39,9 @@ means the end of text in other most regular expression syntaxes. The regular
 expression syntax in Ruby uses ``\A`` for the beginning of text and
 ``\z`` for the end of text.
 
+Groonga uses multiline mode since 5.0.6. It means that ``.`` matches
+on ``\n``.
+
 You can use regular expression in :ref:`select-query` and
 :ref:`select-filter` options of :doc:`/reference/commands/select`
 command.

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/scoring_note.txt

@@ -1,3 +1,5 @@
+:orphan:
+
 .. _note:
 
    You don't need to resolve scoring only by score function. Score

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/sharding.txt

@@ -0,0 +1,108 @@
+.. -*- rst -*-
+
+.. highlightlang:: none
+
+Sharding
+========
+
+.. note::
+
+   This command is an experimental feature.
+
+.. versionadded:: 5.0.0
+
+Groonga has :doc:`/limitations` against table size. You can't add
+268,435,455 more records in one table.
+
+Groonga supports time based sharding to resolve the limitation.
+
+It works in the same database. It doesn't work with multiple
+databases. It means that this sharding feature isn't for distributing
+large data to multiple hosts.
+
+If you want distributed sharding feature, use `Mroonga
+<http://mroonga.org/>`_ or `PGroonga
+<http://pgroonga.github.io/>`_. You can use sharding feature by MySQL
+or PostgreSQL. You'll be able to use `Droonga <http://droonga.org/>`_
+for distributed sharding feature soon.
+
+Summary
+-------
+
+Sharding is implemented in ``sharding`` plugin. The plugin is written
+in mruby. You need to enable mruby when you build Groonga.
+
+You can confirm whether your Groonga supports mruby or not by
+``--version`` command line argument of
+:doc:`/reference/executables/groonga`::
+
+  % groonga --version
+  groonga 5.0.5 [...,mruby,...]
+
+  configure options: <...>
+
+If you find ``mruby``, your Groonga supports mruby.
+
+``sharding`` plugin provides only search commands. They have
+``logical_`` prefix in their command names such as
+:doc:`/reference/commands/logical_select` and
+:doc:`/reference/commands/logical_range_filter`.
+
+``sharding`` plugin doesn't provide schema define commands and data
+load commands yet. You need to use existing commands such as
+:doc:`/reference/commands/table_create`,
+:doc:`/reference/commands/column_create` and
+:doc:`/reference/commands/load`.
+
+``sharding`` plugin requires some rules against table and column. You
+need to follow these rules. They are described later.
+
+.. _sharding-glossary:
+
+Glossary
+--------
+
+.. list-table::
+   :header-rows: 1
+
+   * - Name
+     - Description
+   * - Logical table
+     - It's a table that consists of shards. It doesn't exist in
+       Groonga database. It just exists in our minds.
+   * - Logical table name
+     - The name of logical table. It's prefix of shard names. For
+       example, ``Logs`` is a logical table name and ``Logs_20150814``
+       and ``Logs_20150815`` are shard names.
+   * - Shard
+     - It's a table that has records in a day or month.  One shard has
+       only partial records.
+
+       Shard name (= table name) must follow
+       ``${LOGICAL_TABLE_NAME}_${YYYYMMDD}`` format or
+       ``${LOGICAL_TABLE_NAME}_${YYYYMM}``
+       format. ``${LOGICAL_TABLE_NAME}`` is expanded to logical table
+       name. ``${YYYYMMDD}`` is expanded to day. ``${YYYYMM}`` is
+       expanded to month.
+
+       For example, ``Logs_20150814`` is consists of ``Logs`` logical
+       name and ``20150814`` day.
+
+
+.. _sharding-rules:
+
+Rules
+-----
+
+TODO
+
+.. _sharding-commands:
+
+Commands
+--------
+
+.. toctree::
+   :maxdepth: 1
+   :glob:
+
+   commands/logical_*

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/tokenizers.txt

@@ -515,24 +515,3 @@ index text:
 .. groonga-command
 .. include:: ../example/reference/tokenizers/token-regexp-add.log
 .. tokenize TokenRegexp "/home/alice/test.txt" NormalizerAuto --mode ADD
-
-The beginning of text mark is used for the beginning of text search by
-``\A``. If you use ``TokenRegexp`` for tokenizing query,
-``TokenRegexp`` adds the beginning of text mark (``U+FFEF``) as the
-first token. The beginning of text mark must be appeared at the first,
-you can get results of the beginning of text search.
-
-.. groonga-command
-.. include:: ../example/reference/tokenizers/token-regexp-get-beginning-of-text.log
-.. tokenize TokenRegexp "\\A/home/alice/" NormalizerAuto --mode GET
-
-The end of text mark is used for the end of text search by ``\z``.
-If you use ``TokenRegexp`` for tokenizing query, ``TokenRegexp`` adds
-the end of text mark (``U+FFF0``) as the last token. The end of text
-mark must be appeared at the end, you can get results of the end of
-text search.
-
-.. groonga-command
-.. include:: ../example/reference/tokenizers/token-regexp-get-end-of-text.log
-.. tokenize TokenRegexp "\\.txt\\z" NormalizerAuto --mode GET
-

data/vendor/local/share/doc/groonga/ja/html/_sources/reference/tuning.txt

@@ -43,7 +43,7 @@ Here is an example schema::
   table_create Entries TABLE_HASH_KEY ShortText
   column_create Entries content COLUMN_SCALAR Text
   column_create Entries n_likes COLUMN_SCALAR UInt32
-  table_create Terms TABLE_PAT_KEY|KEY_NORMALIZE ShortText --default_tokenizer TokenBigram
+  table_create Terms TABLE_PAT_KEY ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
   column_create Terms entries_key_index COLUMN_INDEX|WITH_POSITION Entries _key
   column_create Terms entries_content_index COLUMN_INDEX|WITH_POSITION Entries content
 

data/vendor/local/share/doc/groonga/ja/html/_sources/spec/search.txt

@@ -100,7 +100,7 @@ TokenMeCabトークナイザーの場合はわかち書き後のキーワード
 検索の使い分け
 --------------
 
-groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定の閾値以下の場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値以下の場合は部分一致検索を行います。（閾値のデフォルト値は0です。）
+Groongaは基本的に完全一致検索のみを行います。完全一致検索でのヒット件数が所定の閾値以下の場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値以下の場合は部分一致検索を行います。（閾値のデフォルト値は0です。）
 
 ただし、すでに検索結果セットが存在する場合はたとえヒット件数が閾値以下でも完全一致検索のみを行います。
 

data/vendor/local/share/doc/groonga/ja/html/_sources/troubleshooting/different_results_with_the_same_keyword.txt

@@ -17,7 +17,7 @@ DDLは以下の通りです。BlogsテーブルのbodyカラムをTokenMecabト
   table_create Blogs TABLE_NO_KEY
   column_create Blogs body COLUMN_SCALAR ShortText
   column_create Blogs updated_at COLUMN_SCALAR Time
-  table_create Terms TABLE_PAT_KEY|KEY_NORMALIZE ShortText --default_tokenizer TokenMecab
+  table_create Terms TABLE_PAT_KEY ShortText --default_tokenizer TokenMecab  --normalizer NormalizerAuto
   column_create Terms blog_body COLUMN_INDEX|WITH_POSITION Blogs body
 
 テスト用のデータは1件だけ投入します。::
@@ -56,7 +56,7 @@ DDLは以下の通りです。BlogsテーブルのbodyカラムをTokenMecabト
 2. 非わかち書き検索
 3. 部分一致検索
 
-groongaは基本的に完全一致検索のみを行います。上記の例では「東京都民に深刻なダメージを与えました。」を「東京都」というクエリで検索していますが、TokenMecabトークナイザーを使っている場合はこのクエリはマッチしません。
+Groongaは基本的に完全一致検索のみを行います。上記の例では「東京都民に深刻なダメージを与えました。」を「東京都」というクエリで検索していますが、TokenMecabトークナイザーを使っている場合はこのクエリはマッチしません。
 
 検索対象の「東京都民に深刻なダメージを与えました。」は
 
@@ -68,7 +68,7 @@ groongaは基本的に完全一致検索のみを行います。上記の例で
 
 とトークナイズされるため、完全一致しません。
 
-groongaは完全一致検索した結果のヒット件数が所定の閾値を超えない場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値を超えない場合は部分一致検索を行います（閾値は1がデフォルト値となっています）。このケースのデータは部分一致検索ではヒットするので、「東京都」クエリのみを指定するとヒットします。
+Groongaは完全一致検索した結果のヒット件数が所定の閾値を超えない場合に限り、非わかち書き検索を行い、それでもヒット件数が閾値を超えない場合は部分一致検索を行います（閾値は1がデフォルト値となっています）。このケースのデータは部分一致検索ではヒットするので、「東京都」クエリのみを指定するとヒットします。
 
 しかし、以下のように全文検索前にすでに閾値が越えている場合（「updated_at < 1285858800」で1件ヒットし、閾値を越える）は、たとえ完全一致検索で1件もヒットしない場合でも部分一致検索などを行いません。::
 
@@ -85,7 +85,7 @@ TokenMecabトークナイザーは事前に準備した辞書を用いてトー
 
 ここでも、前述の例を使って具体例を示します。まず、TokenBigramを用いた索引を追加します。::
 
-  table_create Bigram TABLE_PAT_KEY|KEY_NORMALIZE ShortText --default_tokenizer TokenBigram
+  table_create Bigram TABLE_PAT_KEY ShortText --default_tokenizer TokenBigram  --normalizer NormalizerAuto
   column_create Bigram blog_body COLUMN_INDEX|WITH_POSITION Blogs body
 
 この状態でも以前はマッチしなかったレコードがヒットするようになります。::

data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/introduction.txt

@@ -19,7 +19,7 @@ Form::
 
   groonga -n DB_PATH
 
-The `-n` option specifies to create a new database and DB_PATH specifies the path of the new database. Actually, a database consists of a series of files and DB_PATH specifies the file which will be the entrance to the new database. DB_PATH also specifies the path prefix for other files. Note that database creation fails if DB_PATH points to an existing file.
+The ``-n`` option specifies to create a new database and DB_PATH specifies the path of the new database. Actually, a database consists of a series of files and DB_PATH specifies the file which will be the entrance to the new database. DB_PATH also specifies the path prefix for other files. Note that database creation fails if DB_PATH points to an existing file (For example, ``db open failed (DB_PATH): syscall error 'DB_PATH' (File exists)``. You can operate an existing database in a way that is in the next chapter).
 
 This command creates a new database and then enters into interactive mode in which Groonga prompts you to enter commands for operating that database. You can terminate this mode with Ctrl-d.
 
@@ -51,6 +51,10 @@ Let's see the status of a Groonga process by using a :doc:`/reference/commands/s
 
 As shown in the above example, a command returns a JSON array. The first element contains an error code, execution time, etc. The second element is the result of an operation.
 
+.. note::
+
+   You can format a JSON using additional tools. For example, `grnwrap <https://github.com/michisu/grnwrap>`_, `Grnline <https://github.com/yoshihara/grnline>`_, `jq <http://stedolan.github.io/jq/>`_ and so on.
+
 Command format
 --------------
 
@@ -91,11 +95,11 @@ Create a table
 
 A :doc:`/reference/commands/table_create` command creates a new table.
 
-In most cases, a table has a primary key which must be specified with its data type and index type. 
+In most cases, a table has a primary key which must be specified with its data type and index type.
 
 There are various data types such as integers, strings, etc. See also :doc:`/reference/types` for more details. The index type determines the search performance and the availability of prefix searches. The details will be described later.
 
-Let's create a table. The following example creates a table with a primary key. The `name` parameter specifies the name of the table. The `flags` parameter specifies the index type for the primary key. The `key_type` parameter specifies the data type of the primary key.
+Let's create a table. The following example creates a table with a primary key. The ``name`` parameter specifies the name of the table. The ``flags`` parameter specifies the index type for the primary key. The ``key_type`` parameter specifies the data type of the primary key.
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-3.log
@@ -112,7 +116,7 @@ A :doc:`/reference/commands/select` command can enumerate records in a table.
 .. include:: ../example/tutorial/introduction-4.log
 .. select --table Site
 
-When only a table name is specified with a `table` parameter, a :doc:`/reference/commands/select` command returns the first (at most) 10 records in the table. [0] in the result shows the number of records in the table. The next array is a list of columns. ["_id","Uint32"] is a column of UInt32, named _id. ["_key","ShortText"] is a column of ShortText, named _key.
+When only a table name is specified with a ``table`` parameter, a :doc:`/reference/commands/select` command returns the first (at most) 10 records in the table. [0] in the result shows the number of records in the table. The next array is a list of columns. ["_id","Uint32"] is a column of UInt32, named _id. ["_key","ShortText"] is a column of ShortText, named _key.
 
 The above two columns, _id and _key, are the necessary columns. The _id column stores IDs those are automatically allocated by Groonga. The _key column is associated with the primary key. You are not allowed to rename these columns.
 
@@ -121,7 +125,7 @@ Create a column
 
 A :doc:`/reference/commands/column_create` command creates a new column.
 
-Let's add a column. The following example adds a column to the Site table. The `table` parameter specifies the target table. The `name` parameter specifies the name of the column. The `type` parameter specifies the data type of the column.
+Let's add a column. The following example adds a column to the Site table. The ``table`` parameter specifies the target table. The ``name`` parameter specifies the name of the column. The ``type`` parameter specifies the data type of the column.
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-5.log
@@ -163,15 +167,15 @@ Get a record
 
 A :doc:`/reference/commands/select` command can search records in a table.
 
-If a search condition is specified with a `query` parameter, a :doc:`/reference/commands/select` command searches records matching the search condition and returns the matched records.
+If a search condition is specified with a ``query`` parameter, a :doc:`/reference/commands/select` command searches records matching the search condition and returns the matched records.
 
-Let's get a record having a specified record ID. The following example gets the first record in the Site table. More precisely, the `query` parameter specifies a record whose _id column stores 1.
+Let's get a record having a specified record ID. The following example gets the first record in the Site table. More precisely, the ``query`` parameter specifies a record whose _id column stores 1.
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-8.log
 .. select --table Site --query _id:1
 
-Next, let's get a record having a specified key. The following example gets the record whose primary key is "http://example.org/". More precisely, the `query` parameter specifies a record whose _key column stores "http://example.org/".
+Next, let's get a record having a specified key. The following example gets the record whose primary key is "http://example.org/". More precisely, the ``query`` parameter specifies a record whose _key column stores "http://example.org/".
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-9.log
@@ -188,11 +192,13 @@ The following shows a command which creates a lexicon table named Terms. The dat
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-10.log
-.. table_create --name Terms --flags TABLE_PAT_KEY|KEY_NORMALIZE --key_type ShortText --default_tokenizer TokenBigram
+.. table_create --name Terms --flags TABLE_PAT_KEY --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
 
 The :doc:`/reference/commands/table_create` command takes many parameters but you don't need to understand all of them. Please skip the next paragraph if you are not interested in how it works.
 
-The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. The KEY_NORMALIZE flag specifies to normalize index terms. In this example, both flags are validated by using a '|'. The `default_tokenizer` parameter specifies the method for tokenizing text. This example uses TokenBigram that is generally called N-gram.
+The TABLE_PAT_KEY flag specifies to store index terms in a patricia trie. The ``default_tokenizer`` parameter specifies the method for tokenizing text. This example uses TokenBigram that is generally called N-gram.
+
+The ``normalizer`` parameter specifies to normalize index terms.
 
 Create an index column for full text search
 -------------------------------------------
@@ -205,7 +211,7 @@ Let's create an index column. The following example creates an index column for
 .. include:: ../example/tutorial/introduction-11.log
 .. column_create --table Terms --name blog_title --flags COLUMN_INDEX|WITH_POSITION --type Site --source title
 
-The `table` parameter specifies the index table and the `name` parameter specifies the index column. The `type` parameter specifies the target table and the `source` parameter specifies the target column. The COLUMN_INDEX flag specifies to create an index column and the WITH_POSITION flag specifies to create a full inverted index, which contains the positions of each index term. This combination, COLUMN_INDEX|WITH_POSITION, is recommended for the general purpose.
+The ``table`` parameter specifies the index table and the ``name`` parameter specifies the index column. The ``type`` parameter specifies the target table and the ``source`` parameter specifies the target column. The COLUMN_INDEX flag specifies to create an index column and the WITH_POSITION flag specifies to create a full inverted index, which contains the positions of each index term. This combination, COLUMN_INDEX|WITH_POSITION, is recommended for the general purpose.
 
 .. note::
 
@@ -216,7 +222,7 @@ Full text search
 
 It's time. You can make full text search with a :doc:`/reference/commands/select` command.
 
-A query for full text search is specified with a `query` parameter. The following example searches records whose "title" column contains "this". The '@' specifies to make full text search. Note that a lower case query matches upper case and capitalized terms in a record if KEY_NORMALIZE was specified when creating a lexcon table.
+A query for full text search is specified with a ``query`` parameter. The following example searches records whose "title" column contains "this". The '@' specifies to make full text search. Note that a lower case query matches upper case and capitalized terms in a record if NormalizerAuto was specified when creating a lexcon table.
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-12.log
@@ -235,7 +241,7 @@ The combination of "`--match_columns` title" and "`--query` this" brings you the
 Specify output columns
 ----------------------
 
-An `output_columns` parameter of a :doc:`/reference/commands/select` command specifies columns to appear in the search result. If you want to specify more than one columns, please separate column names by commas (',').
+An ``output_columns`` parameter of a :doc:`/reference/commands/select` command specifies columns to appear in the search result. If you want to specify more than one columns, please separate column names by commas (',').
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-14.log
@@ -246,9 +252,9 @@ This example specifies three output columns including the _score column, which s
 Specify output ranges
 ---------------------
 
-A :doc:`/reference/commands/select` command returns a part of its search result if `offset` and/or `limit` parameters are specified. These parameters are useful to paginate a search result, a widely-used interface which shows a search result on a page by page basis.
+A :doc:`/reference/commands/select` command returns a part of its search result if ``offset`` and/or ``limit`` parameters are specified. These parameters are useful to paginate a search result, a widely-used interface which shows a search result on a page by page basis.
 
-An `offset` parameter specifies the starting point and a `limit` parameter specifies the maximum number of records to be returned. If you need the first record in a search result, the offset parameter must be 0 or omitted.
+An ``offset`` parameter specifies the starting point and a ``limit`` parameter specifies the maximum number of records to be returned. If you need the first record in a search result, the offset parameter must be 0 or omitted.
 
 .. groonga-command
 .. include:: ../example/tutorial/introduction-15.log
@@ -259,9 +265,9 @@ An `offset` parameter specifies the starting point and a `limit` parameter speci
 Sort a search result
 --------------------
 
-A :doc:`/reference/commands/select` command sorts its result when used with a `sortby` parameter.
+A :doc:`/reference/commands/select` command sorts its result when used with a ``sortby`` parameter.
 
-A `sortby` parameter specifies a column as a sorting creteria. A search result is arranged in ascending order of the column values. If you want to sort a search result in reverse order, please add a leading hyphen ('-') to the column name in a parameter.
+A ``sortby`` parameter specifies a column as a sorting creteria. A search result is arranged in ascending order of the column values. If you want to sort a search result in reverse order, please add a leading hyphen ('-') to the column name in a parameter.
 
 The following example shows records in the Site table in reverse order.
 
@@ -283,4 +289,4 @@ If you want to specify more than one columns, please separate column names by co
 
 .. rubric:: footnote
 
-.. [#] Currently, a `match_columns` parameter is available iff there exists an inverted index for full text search. A `match_columns` parameter for a regular column is not supported.
+.. [#] Currently, a ``match_columns`` parameter is available iff there exists an inverted index for full text search. A ``match_columns`` parameter for a regular column is not supported.

data/vendor/local/share/doc/groonga/ja/html/_sources/tutorial/match_columns.txt

@@ -34,9 +34,9 @@ Then create ``IndexBlog1`` table for column indexes, add ``index_title`` column
 .. column_create --table IndexBlog1 --name index_message --flags COLUMN_INDEX|WITH_POSITION --type Blog1 --source message
 .. load --table Blog1
 .. [
-.. {"_key":"grn1","title":"groonga test","message":"groonga message"},
-.. {"_key":"grn2","title":"baseball result","message":"rakutan eggs 4 - 4 groonga moritars"},
-.. {"_key":"grn3","title":"groonga message","message":"none"}
+.. {"_key":"grn1","title":"Groonga test","message":"Groonga message"},
+.. {"_key":"grn2","title":"baseball result","message":"rakutan eggs 4 - 4 Groonga moritars"},
+.. {"_key":"grn3","title":"Groonga message","message":"none"}
 .. ]
 
 ``match_columns`` option of ``select`` command accepts multiple columns as search target.
@@ -64,13 +64,13 @@ Even though same column index is used, Groonga supports to search against title
 .. table_create --name Blog2 --flags TABLE_HASH_KEY --key_type ShortText
 .. column_create --table Blog2 --name title --flags COLUMN_SCALAR --type ShortText
 .. column_create --table Blog2 --name message --flags COLUMN_SCALAR --type ShortText
-.. table_create --name IndexBlog2 --flags TABLE_PAT_KEY_NORMALIZE --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
+.. table_create --name IndexBlog2 --flags TABLE_PAT_KEY --key_type ShortText --default_tokenizer TokenBigram --normalizer NormalizerAuto
 .. column_create --table IndexBlog2 --name index_blog --flags COLUMN_INDEX|WITH_POSITION|WITH_SECTION --type Blog2 --source title,message
 .. load --table Blog2
 .. [
-.. {"_key":"grn1","title":"groonga test","message":"groonga message"},
-.. {"_key":"grn2","title":"baseball result","message":"rakutan eggs 4 - 4 groonga moritars"},
-.. {"_key":"grn3","title":"groonga message","message":"none"}
+.. {"_key":"grn1","title":"Groonga test","message":"Groonga message"},
+.. {"_key":"grn2","title":"baseball result","message":"rakutan eggs 4 - 4 Groonga moritars"},
+.. {"_key":"grn3","title":"Groonga message","message":"none"}
 .. ]
 
 Let's search same query in previous section. You can get same search results.
@@ -138,9 +138,9 @@ Here is the sample data.
 .. include:: ../example/tutorial/match_columns-nested-index-data.log
 .. load --table Comments
 .. [
-.. {"_key": 1, "content": "I'm using groonga too!"},
-.. {"_key": 2, "content": "I'm using groonga and mroonga!"},
-.. {"_key": 3, "content": "I'm using mroonga too!"}
+.. {"_key": 1, "content": "I'm using Groonga too!"},
+.. {"_key": 2, "content": "I'm using Groonga and Mroonga!"},
+.. {"_key": 3, "content": "I'm using Mroonga too!"}
 .. ]
 .. load --table Articles
 .. [
@@ -193,15 +193,15 @@ Here is the sample data.
 .. include:: ../example/tutorial/match_columns-nested-index-data-with-three-relationship.log
 .. load --table Replies2
 .. [
-.. {"_key": 1, "content": "I'm using rroonga too!"},
-.. {"_key": 2, "content": "I'm using groonga and mroonga and rroonga!"},
-.. {"_key": 3, "content": "I'm using nroonga too!"}
+.. {"_key": 1, "content": "I'm using Rroonga too!"},
+.. {"_key": 2, "content": "I'm using Groonga and Mroonga and Rroonga!"},
+.. {"_key": 3, "content": "I'm using Nroonga too!"}
 .. ]
 .. load --table Comments2
 .. [
-.. {"_key": 1, "content": "I'm using groonga too!", "comment": 1},
-.. {"_key": 2, "content": "I'm using groonga and mroonga!", "comment": 2},
-.. {"_key": 3, "content": "I'm using mroonga too!"}
+.. {"_key": 1, "content": "I'm using Groonga too!", "comment": 1},
+.. {"_key": 2, "content": "I'm using Groonga and Mroonga!", "comment": 2},
+.. {"_key": 3, "content": "I'm using Mroonga too!"}
 .. ]
 .. load --table Articles2
 .. [
@@ -215,16 +215,16 @@ Query for searching the records described above::
   select Articles2 --match_columns comment.content --query mroonga --output_columns "_id, _score, *"
   select Articles2 --match_columns comment.comment.content --query mroonga --output_columns "_id, _score, *"
 
-The first query searches 'mroonga' from Comments2 table, the second one searches 'mroonga' from Replies2 and Comment2 table by using reference column index.
+The first query searches ``mroonga`` from ``Comments2`` table, the second one searches ``mroonga`` from ``Replies2`` and ``Comments2`` table by using reference column index.
 
 .. groonga-command
 .. include:: ../example/tutorial/match_columns-nested-index-select-with-three-relationship.log
 .. select Articles2 --match_columns comment.content --query mroonga --output_columns "_id, _score, *"
 .. select Articles2 --match_columns comment.comment.content --query mroonga --output_columns "_id, _score, *"
 
-As a result, the first query matches two article because of Comments2 table has two records which contains 'mroonga' as keyword.
+As a result, the first query matches two article because of ``Comments2`` table has two records which contains ``mroonga`` as keyword.
 
-On the other hand, the second one matches one article only because of Replies2 table has only one record which contains 'mroonga' as keyword, and there is one record which contains same keyword and refers to the record in Comments2 table.
+On the other hand, the second one matches one article only because of ``Replies2`` table has only one record which contains ``mroonga`` as keyword, and there is one record which contains same keyword and refers to the record in ``Comments2`` table.
 
 Indexes with Weight
 -------------------