Skip to content

Commit f63cbfc

Browse files
committed
minor fixes
1 parent 504612e commit f63cbfc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/search/optimize-search-performance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -96,7 +96,7 @@ _sourceCategory=foo
9696

9797
### Move terms from parse statement to source expression
9898

99-
Adding the parsing terms in the source expression will help you enhance the search performace. A parse statement without `nodrop` drops the logs that could not parse the desired field. For example, `parse “completed * action“ as actionName` will remove logs that do not have **completed** and **action** terms.
99+
Adding the parsing terms in the source expression will help you enhance the search performance. A parse statement without `nodrop` drops the logs that could not parse the desired field. For example, `parse “completed * action“ as actionName` will remove logs that do not have **completed** and **action** terms.
100100

101101
**Recommended approach:**
102102

@@ -138,7 +138,7 @@ _sourceCategory=Prod/User/Eventlog
138138

139139
### Remove redundant operators
140140

141-
Remove the search operators in the query that are not reffered or is not really required for the desired results.
141+
Remove the search operators in the query that are not referred or is not really required for the desired results.
142142

143143
For example, let’s say you have a `sort` operator before an aggregation and this sorting does not make any difference to the aggregated results, resulting in reducing the performance.
144144

0 commit comments

Comments
 (0)