Skip to content

chapter46_part4: /510_Deployment/40_config.asciidoc #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 11 commits into from
May 1, 2016
Merged
2 changes: 1 addition & 1 deletion 130_Partial_Matching/05_Postcodes.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ postcode `W1V 3DG` can((("postcodes (UK), partial matching with"))) be broken do
* `W1V`: This outer part identifies the postal area and district:

** `W` indicates the area (one or two letters)
** `1V` indicates the district (one or two numbers, possibly followed by a letter
** `1V` indicates the district (one or two numbers, possibly followed by a letter)

* `3DG`: This inner part identifies a street or building:

Expand Down
2 changes: 1 addition & 1 deletion 402_Nested/30_Nested_objects.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ The correlation between `Alice` and `31`, or between `John` and `2014-09-01`, ha
from a search point of view, for storing an array of objects.

This is the problem that _nested objects_ are designed to solve. By mapping
the `commments` field as type `nested` instead of type `object`, each nested
the `comments` field as type `nested` instead of type `object`, each nested
object is indexed as a _hidden separate document_, something like this:

[source,json]
Expand Down
Loading