Merge branch 'master' into 1.12-doc-updates

content/dev/contrib_howto.adoc

@@ -25,7 +25,7 @@ Things you should do if you are a Clojure Contrib committer:
 
 * maintain your library and respond to questions/issues that arise
 * do your work on the master branch, or (if you are working on a significant chunk you want to keep temporarily separate) on a feature-specific branch that you create yourself
-* use the Maven Release option on build.clojure.org to make releases
+* use the GitHub "Release on demand" Action to make releases
 * coordinate with other committers before making changes to their libraries
 * accept contributions from others only if they have <<contributors#,signed the CA>>
 

content/dev/contrib_libs.adoc

@@ -14,7 +14,7 @@ These libraries use the same contribution model (<<contributor_agreement#,Contri
 * Source control - Git libraries on GitHub
 * Issues - https://clojure.atlassian.net/projects/CLJ[JIRA]
 * Development model - patches in JIRA, no PRs
-* Continuous integration - https://build.clojure.org[Jenkins]
+* Continuous integration - GitHub actions in each project
 * Doc generation and hosting - https://tomfaulhaber.github.io/autodoc/[Autodoc] and GitHub https://clojure.github.io/[pages]
 * Builds - Maven with deployment to Maven Central under the groupId `org.clojure`
 

content/guides/dev_startup_time.adoc

@@ -24,11 +24,12 @@ The `compile` function takes a namespace symbol and compiles that namespace and
 
 Subsequently, when any of those compiled namespaces are required, the class file will be loaded, rather than the original `.clj` file. If a source file is updated (and thus newer), it will be loaded instead. Periodically, you will need to re-compile to account for new dependencies or changing code.
 
-One special case is the `user.clj` file loaded automatically by the Clojure runtime, before any other code is loaded. If you are using a `user.clj` in dev, you need to force a reload because it has already been loaded automatically:
+Note that compilation is a side effect of loading, so has no effect on already loaded namespaces. In particular, one special case is the `user.clj` file, which is loaded automatically by the Clojure runtime. If you are using a `user.clj` in dev (or need to compile namespaces that are already compiled), you can do so by forcing a reload while compiling:
 
 [source,clojure]
 ----
-(binding [*compile-files* true] (require 'user :reload-all))
+(binding [*compile-files* true] ;; compile during load
+  (require 'user :reload-all))  ;; reload this and all transitively loaded namespaces
 ----
 
 That's it! This technique can substantially reduce your startup time during development, particularly as the number of dependencies you load increases.

content/news/2013/06/28/clojure-clore-async-channels.adoc

@@ -57,7 +57,7 @@ There are analogous operations for use on ordinary threads - http://clojure.gith
 
 === Mixing modes
 
-You can put on a channel from either flavor of `>!`/`>!!` and similarly take with either of `<!`/`<<!` in any combination, i.e. the channel is oblivious to the nature of the threads which use it.
+You can put on a channel from either flavor of `>!`/`>!!` and similarly take with either of `<!`/`<!!` in any combination, i.e. the channel is oblivious to the nature of the threads which use it.
 
 === alt