fix numbered bullet points in faq.md

binaryage · Aug 2, 2016 · 9c2eda4 · 9c2eda4
1 parent f06d2c8
commit 9c2eda4
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/docs/faq.md b/docs/faq.md
@@ -61,9 +61,9 @@ Chrome DevTools support [async call stacks][1]. It would be great to see full ch
 
 There are currently following problems:
 
-1) `core.async` uses `goog.async.nextTick` which is not recognized by Chrome DevTools as async operation participating in async stack traces.
-2) Chrome DevTools UI has hard-coded limit for displaying max 4 chained async stack traces which is not enough for common state-machines generated by `core.async` `go` macros. 
-3) `go-loop` tends to generate state-machines which have very long chains of async stack traces but with repeated patterns for each loop iteration.
+1. `core.async` uses `goog.async.nextTick` which is not recognized by Chrome DevTools as async operation participating in async stack traces.
+2. Chrome DevTools UI has hard-coded limit for displaying max 4 chained async stack traces which is not enough for common state-machines generated by `core.async` `go` macros. 
+3. `go-loop` tends to generate state-machines which have very long chains of async stack traces but with repeated patterns for each loop iteration.
 
 CLJS DevTools cannot solve problems `#2` and `#3`, but it can help with `#1` by monkey-patching `goog.async.nextTick`.