remove {empty}

Author: renetapopova

modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc

@@ -141,7 +141,7 @@ The xref:tools/neo4j-admin/neo4j-admin-import.adoc#import-tool-examples[examples
 | Description
 | Default
 
-|--additional-config=<file>{empty}footnote:[See xref:tools/neo4j-admin/index.adoc#_configuration[Tools -> Configuration] for details.]
+|--additional-config=<file>footnote:[See xref:tools/neo4j-admin/index.adoc#_configuration[Tools -> Configuration] for details.]
 |Configuration file with additional configuration.
 |
 
@@ -160,15 +160,15 @@ For horizontal tabulation (HT), use `\t` or the Unicode character ID `\9`.
 Unicode character ID can be used if prepended by `\`.
 |;
 
-| --auto-skip-subsequent-headers[=true\|false]{empty}footnote:ingnoredByParquet1[Ignored by Parquet import.]
+| --auto-skip-subsequent-headers[=true\|false]footnote:ingnoredByParquet1[Ignored by Parquet import.]
 |Automatically skip accidental header lines in subsequent files in file groups with more than one file.
 |false
 
 |--bad-tolerance=<num>
 |Number of bad entries before the import is aborted. The import process is optimized for error-free data. Therefore, cleaning the data before importing it is highly recommended. If you encounter any bad entries during the import process, you can set the number of bad entries to a specific value that suits your needs. However, setting a high value may affect the performance of the tool.
 |1000
 
-|--delimiter=<char>{empty}footnote:ingnoredByParquet1[]
+|--delimiter=<char>footnote:ingnoredByParquet1[]
 |Delimiter character between values in CSV data. Also accepts `TAB` and e.g. `U+20AC` for specifying a character using Unicode.
 
 ====
@@ -217,11 +217,11 @@ Possible values are:
 |Whether or not empty string fields, i.e. "" from input source are ignored, i.e. treated as null.
 |false
 
-|--ignore-extra-columns[=true\|false]{empty}footnote:ingnoredByParquet1[]
+|--ignore-extra-columns[=true\|false]footnote:ingnoredByParquet1[]
 |If unspecified columns should be ignored during the import.
 |false
 
-|--input-encoding=<character-set>{empty}footnote:ingnoredByParquet1[]
+|--input-encoding=<character-set>footnote:ingnoredByParquet1[]
 |Character set that input data is encoded in.
 |UTF-8
 
@@ -240,11 +240,11 @@ Values can be plain numbers, such as `10000000`, or `20G` for 20 gigabytes.
 It can also be specified as a percentage of the available memory, for example `70%`.
 |90%
 
-|--multiline-fields=true\|false\|<path>[,<path>]{empty}footnote:ingnoredByParquet1[]
+|--multiline-fields=true\|false\|<path>[,<path>]footnote:ingnoredByParquet1[]
 |label:changed[Changed in 5.26] In v1, whether or not fields from an input source can span multiple lines, i.e. contain newline characters. Setting `--multiline-fields=true` can severely degrade the performance of the importer. Therefore, use it with care, especially with large imports. In v2, this option will specify the list of files that contain multiline fields. Files can also be specified using regular expressions.
 |null
 
-|--multiline-fields-format=v1\|v2{empty}footnote:ingnoredByParquet1[]
+|--multiline-fields-format=v1\|v2footnote:ingnoredByParquet1[]
 |label:new[Introduced in 5.26] Controls the parsing of input source that can span multiple lines, i.e. contain newline characters. When set to v1, the value for `--multiline-fields` can only be true or false. When set to v2, the value for `--multiline-fields` should be the list of files that contain multiline fields.
 |null
 
@@ -269,7 +269,7 @@ For an example, see <<import-tool-multiple-input-files-regex-example>>.
 |Delete any existing database files prior to the import.
 |false
 
-|--quote=<char>{empty}footnote:ingnoredByParquet1[]
+|--quote=<char>footnote:ingnoredByParquet1[]
 |Character to treat as quotation character for values in CSV data.
 
 Quotes can be escaped as per link:{rfc-4180}[RFC 4180] by doubling them, for example `""` would be interpreted as a literal `"`.
@@ -344,7 +344,7 @@ If enabled all those relationships will be found but at the cost of lower perfor
 performance, this value should not be greater than the number of available processors.
 |20
 
-|--trim-strings[=true\|false]{empty}footnote:ingnoredByParquet1[]
+|--trim-strings[=true\|false]footnote:ingnoredByParquet1[]
 |Whether or not strings should be trimmed for whitespaces.
 |false
 
@@ -668,7 +668,7 @@ If the database into which you import does not exist prior to importing, you mus
 | Description
 | Default
 
-|--additional-config=<file>{empty}footnote:[See xref:tools/neo4j-admin/index.adoc#_configuration[Tools -> Configuration] for details.]
+|--additional-config=<file>footnote:[See xref:tools/neo4j-admin/index.adoc#_configuration[Tools -> Configuration] for details.]
 |Configuration file with additional configuration.
 |
 
@@ -687,15 +687,15 @@ For horizontal tabulation (HT), use `\t` or the Unicode character ID `\9`.
 Unicode character ID can be used if prepended by `\`.
 |;
 
-| --auto-skip-subsequent-headers[=true\|false]{empty}footnote:ingnoredByParquet2[Ignored by Parquet import.]
+| --auto-skip-subsequent-headers[=true\|false]footnote:ingnoredByParquet2[Ignored by Parquet import.]
 |Automatically skip accidental header lines in subsequent files in file groups with more than one file.
 |false
 
 |--bad-tolerance=<num>
 |Number of bad entries before the import is aborted. The import process is optimized for error-free data. Therefore, cleaning the data before importing it is highly recommended. If you encounter any bad entries during the import process, you can set the number of bad entries to a specific value that suits your needs. However, setting a high value may affect the performance of the tool.
 |1000
 
-|--delimiter=<char>{empty}footnote:ingnoredByParquet2[]
+|--delimiter=<char>footnote:ingnoredByParquet2[]
 |Delimiter character between values in CSV data. Also accepts `TAB` and e.g. `U+20AC` for specifying a character using Unicode.
 
 ====
@@ -742,11 +742,11 @@ Possible values are:
 |Whether or not empty string fields, i.e. "" from input source are ignored, i.e. treated as null.
 |false
 
-|--ignore-extra-columns[=true\|false]{empty}footnote:ingnoredByParquet2[]
+|--ignore-extra-columns[=true\|false]footnote:ingnoredByParquet2[]
 |If unspecified columns should be ignored during the import.
 |false
 
-|--input-encoding=<character-set>{empty}footnote:ingnoredByParquet2[]
+|--input-encoding=<character-set>footnote:ingnoredByParquet2[]
 |Character set that input data is encoded in.
 |UTF-8
 
@@ -765,11 +765,11 @@ Values can be plain numbers, such as `10000000`, or `20G` for 20 gigabytes.
 It can also be specified as a percentage of the available memory, for example `70%`.
 |90%
 
-|--multiline-fields=true\|false\|<path>[,<path>]{empty}footnote:ingnoredByParquet2[]
+|--multiline-fields=true\|false\|<path>[,<path>]footnote:ingnoredByParquet2[]
 |label:changed[Changed in 5.26] In v1, whether or not fields from an input source can span multiple lines, i.e. contain newline characters. Setting `--multiline-fields=true` can severely degrade the performance of the importer. Therefore, use it with care, especially with large imports. In v2, this option will specify the list of files that contain multiline fields. Files can also be specified using regular expressions.
 |null
 
-|--multiline-fields-format=v1\|v2{empty}footnote:ingnoredByParquet2[]
+|--multiline-fields-format=v1\|v2footnote:ingnoredByParquet2[]
 |label:new[Introduced in 5.26] Controls the parsing of input source that can span multiple lines, i.e. contain newline characters. When set to v1, the value for `--multiline-fields` can only be true or false. When set to v2, the value for `--multiline-fields` should be the list of files that contain multiline fields.
 |null
 
@@ -790,7 +790,7 @@ For an example, see <<import-tool-multiple-input-files-regex-example>>.
 |When `true`, non-array property values are converted to their equivalent Cypher types. For example, all integer values will be converted to 64-bit long integers.
 | true
 
-|--quote=<char>{empty}footnote:ingnoredByParquet2[]
+|--quote=<char>footnote:ingnoredByParquet2[]
 |Character to treat as quotation character for values in CSV data.
 
 Quotes can be escaped as per link:{rfc-4180}[RFC 4180] by doubling them, for example `""` would be interpreted as a literal `"`.
@@ -832,7 +832,7 @@ If you need to debug the import, it might be useful to collect the stack trace.
 This is done by using the `--verbose` option.
 |import.report
 
-|--schema=<path>{empty}footnote:[The `--schema` option is available in this version but not yet supported. It will be functional in a future release.]
+|--schema=<path>footnote:[The `--schema` option is available in this version but not yet supported. It will be functional in a future release.]
 |label:new[Introduced in 5.24] Path to the file containing the Cypher commands for creating indexes and constraints during data import.
 |
 
@@ -874,7 +874,7 @@ If enabled all those relationships will be found but at the cost of lower perfor
 performance, this value should not be greater than the number of available processors.
 |20
 
-|--trim-strings[=true\|false]{empty}footnote:ingnoredByParquet2[]
+|--trim-strings[=true\|false]footnote:ingnoredByParquet2[]
 |Whether or not strings should be trimmed for whitespaces.
 |false