branch: elpa/cider
commit b9e48ec979b03bf18725acda53f0553afc5694f2
Author: Bozhidar Batsov <[email protected]>
Commit: Bozhidar Batsov <[email protected]>
[Docs] Fix markup
---
doc/modules/ROOT/pages/troubleshooting.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/modules/ROOT/pages/troubleshooting.adoc
b/doc/modules/ROOT/pages/troubleshooting.adoc
index 9f6e523c3d8..157b9f9cef1 100644
--- a/doc/modules/ROOT/pages/troubleshooting.adoc
+++ b/doc/modules/ROOT/pages/troubleshooting.adoc
@@ -349,6 +349,6 @@ that's due to one of the following reasons:
** You can also, simply, start a repl in the current project.
* There's a bug in the CIDER/Sesman integration
** Session linking generally works by determining whether the current buffer
is related to the classpath of some REPL.
- ** You can obtain debug info echoed to the `*messages*` buffer by running
`M-x cider-debug-sesman-friendly-session-p` on the problematic buffer.
+ ** You can obtain debug info echoed to the `+*Messages*+` buffer by running
`M-x cider-debug-sesman-friendly-session-p` on the problematic buffer.
*** By reading it, you might be able to determine why CIDER failed to see
the relationship between `(buffer-filename)` and the classpath.
*** Feel free to created a detailed GitHub issue including this information.
