Fix compile issues after linting modifications

docs/07-system-internals/02-data-operations/01-write.md

@@ -27,7 +27,7 @@ Trace every part of a write request from beginning to end. This includes:
   - For Ratis:
     - Include topology choices of which Datanodes to use
     - Include failover handling
-  - For [EC](../features/erasure-coding) and [Ratis Streaming](../features/ratis-streaming), link to their feature pages.
+  - For [EC](../features/erasure-coding) and Ratis Streaming, link to their feature pages.
 - Client allocating more blocks if needed
 - Client committing to OM
 - OM checking the current namespace

docs/08-developer-guide/04-project/02-release-guide.md

@@ -279,7 +279,7 @@ Before uploading the artifacts, run some basic tests on them, similar to what ot
     - A significant increase in size could indicate a dependency issue that needs to be fixed.
     - The Apache svn repo has a size limit for release artifacts. If uploading svn fails because the tarball is too big, we need to contact INFRA to increase our repo size. [See here for details.](https://issues.apache.org/jira/browse/INFRA-23892)
 3. Verify signatures
-    - Download the KEYS file from <https://dist.apache.org/repos/dist/release/ozone/KEYS>
+    - Download the KEYS file from https://dist.apache.org/repos/dist/release/ozone/KEYS
     - Import its contents (which should include your public GPG key):
 
       ```bash
@@ -370,8 +370,8 @@ Send a vote email to the dev@ozone.apache.org mailing list. Include the followin
 - Link to the release candidate tag on Github
 - Link to a Jira query showing all resolved issues for this release. Something like [this](https://issues.apache.org/jira/issues/?jql=project%20%3D%20HDDS%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.4.0).
 - Location of the source and binary tarballs. This link will look something like https://dist.apache.org/repos/dist/dev/ozone/1.2.0-rc0
-- Location where the Maven artifacts are staged. This link will look something like <https://repository.apache.org/content/repositories/orgapacheozone-1001/>
-- Link to the public key used to sign the artifacts. This should always be in the KEYS file and you can just link to that: <https://dist.apache.org/repos/dist/dev/ozone/KEYS>
+- Location where the Maven artifacts are staged. This link will look something like https://repository.apache.org/content/repositories/orgapacheozone-1001/
+- Link to the public key used to sign the artifacts. This should always be in the KEYS file and you can just link to that: https://dist.apache.org/repos/dist/dev/ozone/KEYS
 - Fingerprint of the key used to sign the artifacts.
 
 If no issues are found with the artifacts, let the vote run for 7 days. Review the [ASF wide release voting policy](https://www.apache.org/legal/release-policy.html#release-approval), and note the requirements for binding votes which can only come from PMC members. Sometimes responders will not specify whether their vote is binding. If in doubt check the [ASF committer index](https://people.apache.org/committer-index.html). Users whose group membership includes `ozone-pmc` can cast binding votes.
@@ -463,9 +463,9 @@ This step requires the release's [Docker image](#publish-a-docker-image-for-the-
 
 Include the following links:
 
-- Release notes: <https://ozone.apache.org/release/1.2.0/>. Replace the version in the URL with the version being released.
-- Download link: <https://ozone.apache.org/downloads/>
-- Link to versioned documentation: <https://ozone.apache.org/docs/>
+- Release notes: https://ozone.apache.org/release/1.2.0/. Replace the version in the URL with the version being released.
+- Download link: https://ozone.apache.org/downloads/
+- Link to versioned documentation: https://ozone.apache.org/docs/
 
 ## Patch Release