Skip to content

Commit 5d68d88

Browse files
committed
Tweak docs/cider/debugging/logging.html
1 parent ee7bdbd commit 5d68d88

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ To use CIDER Log Mode, there two main ways to get started:
5454
** It doesn't use transient-mode - it aims to do everything in one step
5555
** It immediately shows the `+*cider-log*+` buffer
5656

57-
NOTE: any of these commands will only succeed in
57+
NOTE: Any of these commands will only succeed in
5858
a buffer that has a CIDER repl (https://github.com/vspinu/sesman[Sesman]
5959
session) attached to it.
6060

@@ -70,7 +70,7 @@ By using `M-x cider-log-show`, all setup and rendering will be performed for you
7070

7171
All these steps are idempotent, so it's safe to run `M-x cider-log-show` more than once.
7272

73-
You can refine the setup afterwards (e.g. configuring filtering) by running `M-x cider-log`.
73+
You can refine the setup afterwards (e.g. configuring filtering) by running `M-x cider-log`, `M-x cider-log-consumer`, etc.
7474

7575
=== Via `cider-log-event`
7676

@@ -168,7 +168,7 @@ Timbre support is WIP as well.
168168
TIP: If your logging framework of choice is not currently supported by CIDER Log Mode,
169169
you can opt to use Clojure's official `tools.logging` façade in your project, such that you can locally,
170170
unobstrusively tell it to use a supported framework (like Logback) instead of your project's default one.
171-
Note that `tools.logging`'s choice of logging backend implementation can be controlled with the
171+
Note that its choice of logging backend implementation can be controlled with the
172172
`-Dclojure.tools.logging.factory` Java system property, which can be cleanly customized locally via Lein profiles,
173173
or Clojure CLI aliases.
174174

0 commit comments

Comments
 (0)