Convert remaining <a href...> hyperlinks to markdown

Some of these were enabled by #59; others may have just been
oversights in writing up the articles.

---
Signed-off-by: Brad Chamberlain <bradcray@users.noreply.github.com>

Author: bradcray

content/posts/10myths-part2/index.md

@@ -224,8 +224,7 @@ gap to an acceptable level, and that delay to achieving performance
 led to a lot of doubt and cynicism around Chapel in the 2010's, some
 of which persists to this day.  However, this approach was also an
 investment that has paid off—for example, the recently-added sparse
-features and optimizations <a href =
-"../10myths-part1/#the-sparse-example">mentioned last month</a> were
+features and optimizations [mentioned last month]({{<relref 10myths-part1>}}#the-sparse-example) were
 made with no changes to the compiler thanks to this
 approach.{{</sidenote>}}, with the goal of avoiding a performance
 cliff between “built-in” and user-defined distributions.
@@ -355,9 +354,9 @@ many more memory operations, slowing the application down while
 increasing the program's memory footprint.  They can be optimized away
 using transformations such as
 {{<sidenote "right" "_loop fusion_ and _array contraction_">}}See, for
-example, <a href = "https://dl.acm.org/doi/10.1145/277652.277663">The
+example, [The
 implementation and evaluation of fusion and contraction in array
-languages</a> by E Christopher Lewis, Calvin Lin, and Lawrence Snyder
+languages](https://dl.acm.org/doi/10.1145/277652.277663) by E Christopher Lewis, Calvin Lin, and Lawrence Snyder
 in <i>Proceedings of the ACM Conference on Programming Language Design
 and Implementation</i>, 1998.{{</sidenote>}}, resulting in performance
 that competes with hand-generated loops.  But these optimizations can

content/posts/changes-since-2.0-rc1/index.md

@@ -253,7 +253,7 @@ this that may be unsafe.
 
 #### Class Memory Management
 
-For the last few Chapel releases using stable features, it was not possible to escape the <a href="https://chapel-lang.org/docs/1.33/technotes/lifetimeChecking.html">lifetime checker</a>
+For the last few Chapel releases using stable features, it was not possible to escape the [lifetime checker](https://chapel-lang.org/docs/1.33/technotes/lifetimeChecking.html">lifetime checker)
 when using managed classes like `owned` and `shared`. These
 management strategies use the lifetime checker to ensure that memory is not
 accessed incorrectly. It is sometimes necessary to have pieces of code that a

content/posts/fortran-marbl1/index.md

@@ -69,8 +69,8 @@ Finally, we can use our Fortran subroutines in Chapel. Let's populate an array a
 {{< file_download fname="sequential.chpl" lang="chapel">}}
 
 {{<sidenote "right" "" -15 >}}
-These signatures were generated manually. Alternatively, the <code><a href = "https://chapel-lang.org/docs/tools/c2chapel/c2chapel.html">c2chapel</a></code> tool can be used to generate <code>extern</code> declarations automatically, or an 
-<a href = "https://chapel-lang.org/docs/technotes/extern.html#support-for-extern-blocks"><i>extern block</i></a> can be used to have the Chapel compiler parse the C header file contents directly.
+These signatures were generated manually. Alternatively, the [`c2chapel`](https://chapel-lang.org/docs/tools/c2chapel/c2chapel.html) tool can be used to generate <code>extern</code> declarations automatically, or an 
+[_extern block_](https://chapel-lang.org/docs/technotes/extern.html#support-for-extern-blocks) can be used to have the Chapel compiler parse the C header file contents directly.
 {{< /sidenote >}}
 
 {{< details summary="**Click here for help interpreting the Chapel code**" >}}