Address review comments

Author: varungandhi-src

docs/code-search/code-navigation/inference_configuration.mdx

@@ -235,17 +235,17 @@ them without good reason. So it's better to have them at least
 reach out to us first, and we can advise them on a case-by-case basis.
 -->
 
-If the number of auto-indexing jobs and/or paths exceeds these limits, excess jobs and/or paths will be sorted based on the following ordering and trailing jobs will be discarded:
+Auto-indexing jobs and paths are first ranked based on the criteria described below. If the number of jobs and/or paths exceeds the limits above, lower ranked items are discarded.
 
-- For auto-indexing jobs, sorting happens in the following order:
+- For auto-indexing jobs, ranking is done based on the following:
 
   - Descending order of indexer frequency (total number of inferred jobs with the same `indexer` field).
-  - Lexicographic ordering of `indexer`.
+  - Ascending lexicographic ordering of `indexer`.
   - Descending order of number of path components for `root`. Shallower roots are preferrred over deeper ones as they are more likely to cover more code.
-  - Lexicographic ordering of `root` paths.
+  - Ascending lexicographic ordering of `root` paths.
 
-- For paths, sorting happens in the following order:
+- For paths, ranking happens in the following order:
 
-  - Paths for which the contents are requested come before other paths.
-  - Paths with fewer components come before paths with more components.
-  - Otherwise, paths are ordered lexicographically.
+  - Paths for which the contents are requested are ranked higher.
+  - Paths with fewer components are ranked higher.
+  - Otherwise, lexicographic ordering of paths is used.