[DOCS][8.x] Fix dodgy backticks + move tip (#127555) (#127557)

* [DOCS][8.x] Fix dodgy backticks

h/t @alex-spies

* Move tip

docs/reference/esql/esql-lookup-join.asciidoc

@@ -79,7 +79,7 @@ contains multi-valued entries, those entries will not match anything
 image::images/esql/esql-lookup-join.png[align="center"]
 
 If you're familiar with SQL, `LOOKUP JOIN` has left-join behavior. This means that 
-if no rows match in the lookup index, the incoming row is retained and `null`s are added. If many rows in the lookup index match, `LOOKUP JOIN` adds one row per match.
+if no rows match in the lookup index, the incoming row is retained and `null` values are added. If many rows in the lookup index match, `LOOKUP JOIN` adds one row per match.
 
 [discrete]
 [[esql-lookup-join-example]]
@@ -251,4 +251,4 @@ in the lookup index, or if the documents are too large. More precisely,
 `LOOKUP JOIN` works in batches of, normally, about 10,000 rows; a large
 amount of heap space is needed if the matching documents from the lookup
 index for a batch are multiple megabytes or larger. This is roughly the
-same as for `ENRICH`.
+same as for `ENRICH`.

docs/reference/esql/processing-commands/lookup.asciidoc

@@ -48,13 +48,13 @@ added as new columns to that row.
 If multiple documents in the lookup index match a single row in your
 results, the output will contain one row for each matching combination.
 
-*Examples*
-
 [TIP]
 ====
 In case of name collisions, the newly created columns will override existing columns.
 ====
 
+*Examples*
+
 *IP Threat correlation*: This query would allow you to see if any source
 IPs match known malicious addresses.