Skip to content

Commit 4a30c20

Browse files
committed
fix link, tweak wording
1 parent 87ef558 commit 4a30c20

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/reference/query-languages/esql/_snippets/commands/layout/lookup-join.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ If multiple documents in the lookup index match a single row in your
4242
results, the output will contain one row for each matching combination.
4343

4444
::::{tip}
45-
For important information about using `LOOKUP JOIN`, refer to [Usage notes](../../../../esql/esql-lookup-join.md#implementation-details).
45+
For important information about using `LOOKUP JOIN`, refer to [Usage notes](../../../../esql/esql-lookup-join.md#usage-notes).
4646
::::
4747

4848
**Examples**

docs/reference/query-languages/esql/esql-lookup-join.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -163,10 +163,10 @@ This section covers important details about `LOOKUP JOIN` that impact query beha
163163
### Handling name collisions
164164

165165
When fields from the lookup index match existing column names, the new columns override the existing ones.
166-
Before the `LOOKUP JOIN`, preserve columns by either:
166+
Before the `LOOKUP JOIN` command, preserve columns by either:
167167

168168
* Using `RENAME` to assign non-conflicting names
169-
* Using `EVAL` to create new columns with different names, then `DROP` the original columns
169+
* Using `EVAL` to create new columns with different names, then `DROP` to remove the original columns
170170

171171
### Sorting behavior
172172

0 commit comments

Comments
 (0)