lisp: export latest after fixing external replacement

lispprogrammingguide.md

@@ -1,6 +1,5 @@
 # Google Common Lisp Effective Programming
 
-
 ## Introduction
 
 This document is intended as a supplement to the
@@ -36,7 +35,6 @@ new Lisp programmers.
     software you're writing, and must not be considered available for use. Be
     aware of these issues, or consult with people who are.
 
-
 ### Avoid Allocation
 
 -   Make sure objects are no longer reachable after they're no longer needed.
@@ -109,7 +107,6 @@ and slower optimize settings; this is good to locate a dynamic error in your
 code during development, but is not to be used for production code since it
 defeats the purpose of declarations as a performance trick.
 
-
 ### DYNAMIC-EXTENT
 
 -   Treat `DYNAMIC-EXTENT` as an unsafe operation, profile any code using it and
@@ -221,7 +218,6 @@ from a suitable library (that you may have to contribute to) that properly
 handles those cases without burdening users with implementation details. See for
 instance `UIOP:REDUCE/STRCAT`.
 
-
 ### NCONC and MAPCAN
 
 -   Don't use `NCONC` or `MAPCAN`.
@@ -336,7 +332,6 @@ complexities and rounding errors of floating-point arithmetic. Libraries such as
 this library is not satisfactory, see above about
 [Using Libraries](#using-libraries).
 
-
 ### Case and Ecase
 
 -   Use `CASE` and `ECASE` for numbers, characters, and symbols only.
@@ -522,7 +517,6 @@ ways. You should use other pathname abstractions, such as
 `ASDF:SYSTEM-RELATIVE-PATHNAME` or the underlying `UIOP:SUBPATHNAME` and
 `UIOP:PARSE-UNIX-NAMESTRING`.
 
-
 Finally, be aware that paths may change between the time you build the Lisp
 image for your application, and the time you run the application from its image.
 You should be careful to reset your image to forget irrelevant build-time paths
@@ -531,7 +525,6 @@ instance requires you to reset its paths with `UIOP:CLEAR-CONFIGURATION`. `UIOP`
 provides hooks to call functions before an image is dumped, from which to reset
 or `makunbound` relevant variables.
 
-
 ### SATISFIES
 
 -   You must be careful when using a `SATISFIES` clause in a type specifier.