Skip to content

Commit 5fb6475

Browse files
committed
Fix some markup
1 parent a472c80 commit 5fb6475

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -695,7 +695,7 @@ be concise, but won't carry much meaning).
695695
But what to do about all the other namespaces out there that don't have idiomatic aliases? Well, you better be consistent in your approach to deriving aliases for them,
696696
otherwise the people working on a shared Clojure codebase are going to experience a great deal of confusion. Here are a few rules that you should follow.footnote:[These guidelines are based on a https://stuartsierra.com/2015/05/10/clojure-namespace-aliases[blog post] by Stuart Sierra.]
697697

698-
. Make the alias the same as the namespace name with the leading parts removed.
698+
1. Make the alias the same as the namespace name with the leading parts removed.
699699

700700
[source,clojure]
701701
----
@@ -705,7 +705,7 @@ otherwise the people working on a shared Clojure codebase are going to experienc
705705
[clojure.string :as string]))
706706
----
707707

708-
. Keep enough trailing parts to make each alias unique.
708+
2. Keep enough trailing parts to make each alias unique.
709709

710710
[source,clojure]
711711
----
@@ -715,7 +715,7 @@ otherwise the people working on a shared Clojure codebase are going to experienc
715715

716716
TIP: Yes, namespace aliases can have dots in them. Make good use of them.
717717

718-
. Eliminate redundant words such as "core" and "clj" in aliases.
718+
3. Eliminate redundant words such as "core" and "clj" in aliases.
719719

720720
[source,clojure]
721721
----

0 commit comments

Comments
 (0)