Changes in b627dc5: WellKnownIdentifier: edits

				WellKnownIdentifier.md
			
          @@ -11,7 +11,7 @@ of band information.

           The description of this pattern is inspired by [Well-Known Uniform Resource

           Identifiers](https://en.wikipedia.org/wiki/Well-known_URI), by recognizing that

           this is a more general pattern. Once you start looking for it you will discover

          -it in very different kind of contexts.

          +it in very different kinds of contexts.

           Some of the examples may seem trite and obvious, but we think it's useful to

           recognize the common pattern across different contexts, to consider why this

          @@ -102,10 +102,10 @@ identifier that's specific to one tool, it's a mechanism that could be leveraged

           more generally.

           Similarly JVM system properties that are understood by mutiple libraries/tools

          -seems to be an underutilized mechanisms.

          +seems to be an underutilized mechanism.

           There are several commonly used well-known environment variables. Most software

          -intended to run in a cloud environment understand the `PORT` variable to decide

          +intended to run in a cloud environment understands the `PORT` variable to decide

           which HTTP port to run on. Most CI environments set the `CI` variable to signal

           that the code is being run on CI.

          @@ -138,8 +138,8 @@ strongly encourage anyone adopting these tools

           [Kaocha](https://github.com/lambdaisland/launchpad)), to create these two

           executables within their projects. 

          -We sometimes get questions about that. Why not use `clj -X:kaocha`, or `bb run

          -launchpad`. The problem with these is that they are not general enough. Not

          +We sometimes get questions about that. Why not use `clj -X:kaocha`, or

          +`bb run launchpad`. The problem with these is that they are not general enough. Not

           every project uses Clojure CLI or Babashka. By having an executable path that is

           independent of the concrete tooling we create an abstraction. From the

           programmer's point of view they can invoke Kaocha the same way on any project.

          @@ -151,9 +151,9 @@ Besides invoking the appropriate Clojure launcher, they can perform additional

           steps. For instance, it's common for `bin/kaocha` to run `npm install` when

           needed.

          -In [[Gaiwan Corgi]] we have the key combination `,,` to evaluate a snippet

          -that's stored in a register, and we set some registers so we can easily invoke

          -some of the above.

          +In [Gaiwan's Corgi Setup](https://github.com/GaiwanTeam/emacs.d) we have the key

          +combination `,,` to evaluate a snippet that's stored in a register, and we set

          +some registers so we can easily invoke some of the above.

           - `,,g` - runs `(user/go)`

           - `,,b` - runs `(user/browse)`

...	...	@@ -11,7 +11,7 @@ of band information.
11	11	The description of this pattern is inspired by [Well-Known Uniform Resource
12	12	Identifiers](https://en.wikipedia.org/wiki/Well-known_URI), by recognizing that
13	13	this is a more general pattern. Once you start looking for it you will discover
14		-it in very different kind of contexts.
	14	+it in very different kinds of contexts.
15	15
16	16	Some of the examples may seem trite and obvious, but we think it's useful to
17	17	recognize the common pattern across different contexts, to consider why this
...	...	@@ -102,10 +102,10 @@ identifier that's specific to one tool, it's a mechanism that could be leveraged
102	102	more generally.
103	103
104	104	Similarly JVM system properties that are understood by mutiple libraries/tools
105		-seems to be an underutilized mechanisms.
	105	+seems to be an underutilized mechanism.
106	106
107	107	There are several commonly used well-known environment variables. Most software
108		-intended to run in a cloud environment understand the `PORT` variable to decide
	108	+intended to run in a cloud environment understands the `PORT` variable to decide
109	109	which HTTP port to run on. Most CI environments set the `CI` variable to signal
110	110	that the code is being run on CI.
111	111
...	...	@@ -138,8 +138,8 @@ strongly encourage anyone adopting these tools
138	138	[Kaocha](https://github.com/lambdaisland/launchpad)), to create these two
139	139	executables within their projects.
140	140
141		-We sometimes get questions about that. Why not use `clj -X:kaocha`, or `bb run
142		-launchpad`. The problem with these is that they are not general enough. Not
	141	+We sometimes get questions about that. Why not use `clj -X:kaocha`, or
	142	+`bb run launchpad`. The problem with these is that they are not general enough. Not
143	143	every project uses Clojure CLI or Babashka. By having an executable path that is
144	144	independent of the concrete tooling we create an abstraction. From the
145	145	programmer's point of view they can invoke Kaocha the same way on any project.
...	...	@@ -151,9 +151,9 @@ Besides invoking the appropriate Clojure launcher, they can perform additional
151	151	steps. For instance, it's common for `bin/kaocha` to run `npm install` when
152	152	needed.
153	153
154		-In [[Gaiwan Corgi]] we have the key combination `,,` to evaluate a snippet
155		-that's stored in a register, and we set some registers so we can easily invoke
156		-some of the above.
	154	+In [Gaiwan's Corgi Setup](https://github.com/GaiwanTeam/emacs.d) we have the key
	155	+combination `,,` to evaluate a snippet that's stored in a register, and we set
	156	+some registers so we can easily invoke some of the above.
157	157
158	158	- `,,g` - runs `(user/go)`
159	159	- `,,b` - runs `(user/browse)`