docs: fix typo (docarray#325)

k-zehnder · web-flow · commit 08d0072b4b4f · 2022-05-03T20:44:42.000+02:00
diff --git a/docs/fundamentals/documentarray/access-elements.md b/docs/fundamentals/documentarray/access-elements.md
@@ -135,7 +135,7 @@ da['@path1,path2,path3']
 
 - The path-string must starts with `@`.
 - Multiple paths are separated by comma `,`.
-- A path represents the route from the top-level Documents to the destination. You can use `c` to select chunks, `cc` to select chunks of the chunks, `m` to select matches, `mc` to select matches of the chunks, `r` to select the top-level Documents.
+- A path represents the route from the top-level Documents to the destination. You can use `c` to select chunks, `cc` to select chunks of the chunks, `m` to select matches, `mc` to select chunks of the matches, `r` to select the top-level Documents.
 - A path can only go deep, not go back. You can use comma `,` to start a new path from the very top-level.
 - Optionally, you can specify a slice or offset at each level, for example, `r[-1]m[:3]` will select the first 3 matches of the last root document.
 
diff --git a/docs/fundamentals/documentarray/matching.md b/docs/fundamentals/documentarray/matching.md
@@ -23,7 +23,7 @@ Though both `.find()` and `.match()` is about finding nearest neighbours of a gi
 
 ##### What is the return?
   - `.find()` returns a List of DocumentArray, each of which corresponds to one element/row in the query.
-  - `.match()` do not return anything. Match results are stored inside right-hand side's `.matches`.
+  - `.match()` do not return anything. Match results are stored inside left-hand side's `.matches`.
 
 In the sequel, we will use `.match()` to describe the features. But keep in mind that `.find()` should also work by simply switching the right and left-hand sides.
 
