Fix jnewbery's crass merge error

Author: jnewbery

Makefile

@@ -23,7 +23,7 @@ test-before-build:
 	! git --no-pager grep -h "^slug: " _posts | sort | uniq -d | grep .
 	## Check for things that should probably all be on one line
 	@ ## Note: double $$ in a makefile produces a single literal $
-	! git --no-pager grep -- '^ *- \*\*[^\*]*$$'
+	! git --no-pager grep -- '^ *- \*\*[^*]*$$'
 	! git --no-pager grep -- '^ *- \[[^]]*$$'
 
 	## Check that newly added or modifyed PNGs are optimized

_posts/en/newsletters/2018-10-30-newsletter.md

@@ -205,7 +205,8 @@ it to write a good description, and I doubt non-LN devs care -->{% endcomment %}
 - [LND #1981][] ensures that LND doesn't leak information about any of
   its peers that aren't advertising themselves as public nodes.
 
-- LND [#1535][LND #1535] and [#1512][LND #1512] adds the server-side
+- {:#lnd-1535-1512}
+  LND [#1535][LND #1535] and [#1512][LND #1512] adds the server-side
   communication protocol for watchtowers along with many tests verifying
   its proper operation.  Correct use of the LN protocol requires regular
   monitoring of which transactions get added to the block chain, so
@@ -216,7 +217,6 @@ it to write a good description, and I doubt non-LN devs care -->{% endcomment %}
   specification for watchtowers has not been agreed upon by the multiple
   implementations of LN, so LND is only putting this feature out for
   initial testing and is restricting its use to testnet.
-  {:#lnd-1535-1512}
 
 {% include references.md %}
 {% include linkers/issues.md issues="14451,14296,14468,14150,1981,1535,1512" %}

_posts/en/newsletters/2018-12-28-newsletter.md

@@ -331,7 +331,7 @@ recommended) using Tor---which can provide other benefits---but enabling
 encryption by default could help protect a larger number of users from
 eavesdropping by their ISPs.
 
-{:#untrackable-auth}
+{:#countersign}
 Separately, Pieter Wuille has been working on a [draft document][untrackable auth]
 since February based on a protocol he, Gregory Maxwell, and others have been developing
 to allow optional authentication on top of encryption.  Similar to

_posts/en/newsletters/2019-06-12-newsletter.md

@@ -38,10 +38,11 @@ changes to popular Bitcoin infrastructure projects.
       addresses, tracking when they've been paid, and finding or
       deriving the particular private keys necessary for spending.
 
-    - <span id="cleanup-discussion" markdown="1">June 6th: discussion of the [consensus cleanup soft fork][xs
+    - June 6th: discussion of the [consensus cleanup soft fork][xs
       cleanup sf] included its interaction with [bip-taproot][], whether
       parts of it should be dropped, and whether anything should be
-      added.  ([More background][bg consensus cleanup])</span>
+      added.  ([More background][bg consensus cleanup])
+      {:#cleanup-discussion}
 
       The group asked what they could do to make the [maintainers'][xs
       maint] work easier.  Among other considerations, the maintainers
@@ -67,9 +68,10 @@ changes to popular Bitcoin infrastructure projects.
       UTXO set highlighted some interesting details of this developing
       proposal for minimizing full node storage requirements.
 
-    - <span id="assume-utxo-demo" markdown="1">June 7th: code for the [assumeutxo][xs assumeutxo] proposal was
+    - June 7th: code for the [assumeutxo][xs assumeutxo] proposal was
       demoed and discussed, including how to make the proposal
-      compatible with other ideas. ([More background][bg assumeutxo])</span>
+      compatible with other ideas. ([More background][bg assumeutxo])
+      {:#assume-utxo-demo}
 
       {:#hwi}
       Contributors discussed getting [hardware wallet][xs hwi] support