Skip to content

Commit b6e7786

Browse files
rechvsbbatsov
authored andcommitted
Improve wording in docs
The concatenation of "for" and "of" was a bit difficult to follow/understand.
1 parent 14923cb commit b6e7786

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

doc/modules/ROOT/pages/debugging/inspector.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
11
= Inspector
22
:experimental:
33

4-
The value inspector allows you inspect and navigate the structure of data. While you can use
4+
The value inspector allows you to inspect and navigate the structure of data. While you can use
55
it for pretty much anything (e.g. primitive data types, var, ref types) it's most
66
useful when you're dealing with (deeply) nested collection-like data types (e.g. a vector of maps).
77

88
== Usage
99

1010
Typing kbd:[C-c M-i] (`cider-inspect`) after some form in a source
11-
buffer or the REPL will show you the structure for the result of the
12-
form in a new buffer. You can also use kbd:[C-u C-c M-i] to inspect
11+
buffer or the REPL will show you the structure of the form's result
12+
in a new buffer. You can also use kbd:[C-u C-c M-i] to inspect
1313
the result of the current top-level form and kbd:[C-u C-u C-c M-i] to
1414
read an expression from the minibuffer and inspect its result.
1515

1616
Alternatively, after a regular eval command, you can inspect the last
17-
evaluated value using `cider-inspect-last-result`. When a inspector
17+
evaluated value using `cider-inspect-last-result`. When an inspector
1818
buffer is visible in the background, it is automatically updated with
1919
the last result. This behavior can be controlled with the variable
2020
`cider-auto-inspect-after-eval`.

0 commit comments

Comments
 (0)