From eea8d6de46510c56ded470e92d86c4e5116b4457 Mon Sep 17 00:00:00 2001
From: Tony Solomonik <tony.solomonik@gmail.com>
Date: Fri, 30 Aug 2024 16:26:09 +0300
Subject: [PATCH] fix concatenate field docs

---
 docs/configuration/index-config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/configuration/index-config.md b/docs/configuration/index-config.md
index ef6383c06cb..5dbc7db8ade 100644
--- a/docs/configuration/index-config.md
+++ b/docs/configuration/index-config.md
@@ -424,7 +424,7 @@ to the field being searched.
 ```yaml
 name: my_default_field
 type: concatenate
-concatenated_fields:
+concatenate_fields:
   - text # things inside text, tokenized with the `default` tokenizer
   - resource.author # all fields in resource.author, assuming resource is an `object` field.
 include_dynamic_fields: true
@@ -435,7 +435,7 @@ record: basic
 Concatenate fields don't support fast fields, and are never stored. They uses their own tokenizer, independently of the
 tokenizer configured on the individual fields.
 At query time, concatenate fields don't support range queries.
-Only the following types are supported inside a concatenate field: text, bool, i64, u64, json. Other types are rejected
+Only the following types are supported inside a concatenate field: text, bool, i64, u64, f64, json. Other types are rejected
 at index creation, or silently discarded during indexation if they are found inside a json field.
 Adding an object field to a concatenate field doesn't automatically add its subfields (yet).
 <!-- typing is made so it wouldn't be too hard do add, as well as things like params_* matching all fields which starts name with params_ , but the feature isn't implemented yet -->