[olingo-site] 04/15: fix typos

[wa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

wave pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/olingo-site.git

commit 71fb1759d5becc264d5ace361ae70276ac4f009f
Author: Dave Fisher <da...@davefisher.tech>
AuthorDate: Fri Jun 4 09:48:29 2021 -0700

    fix typos
---
 content/doc/odata2/release.md                          | 4 ++--
 content/doc/odata4/release.md                          | 2 +-
 content/doc/odata4/tutorials/od4_quick_start_sample.md | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/doc/odata2/release.md b/content/doc/odata2/release.md
index e6ceb30..2814e80 100644
--- a/content/doc/odata2/release.md
+++ b/content/doc/odata2/release.md
@@ -21,7 +21,7 @@ An Apache Olingo release consists of:
 
   * All POMs/JARs/WARs built as part of the standard Maven build process. For
 an overview on the released modules see artifacts with groupId
-_org.apache.olingo_ in the [Apache Maven Repository](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo```~).
+_org.apache.olingo_ in the [Apache Maven Repository](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~~~~).
 In detail, per every module, where applicable, the following artifacts are produced:
    * **Main artifact**: `<artifactId>-<version>.<ext>`
    * **Source artifact**: `<artifactId>-<version>-sources.<ext>`
@@ -189,7 +189,7 @@ Of course the Release Manager can also use this checklist to make sure all artif
 If the release candidate gets approved, we can proceed to release publishing:
 
   - Release candidate maven artifacts are promoted in the Apache Maven Repository and
-made available [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo```~).
+made available [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~~~~).
   - Publish final release Version to [Apache Repository](https://repository.apache.org/)
     - First publish via `mvn deploy -Papache-release` into the *Staging Area*
     - From *Staging Area* close and release the staged Artifacts to finish publishing
diff --git a/content/doc/odata4/release.md b/content/doc/odata4/release.md
index 0ec191c..f34f2ec 100644
--- a/content/doc/odata4/release.md
+++ b/content/doc/odata4/release.md
@@ -179,7 +179,7 @@ Of course the Release Manager can also use this checklist to make sure all artif
 If the release candidate gets approved, we can proceed to release publishing:
 
   - Release candidate maven artifacts are promoted in the Apache Maven Repository and
-made available [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo```~).
+made available [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~~~~).
   - Publish final release Version to [Apache Repository](https://repository.apache.org/)
     - First publish via `mvn deploy -Papache-release` into the *Staging Area*
     - From *Staging Area* close and release the staged Artifacts to finish publishing
diff --git a/content/doc/odata4/tutorials/od4_quick_start_sample.md b/content/doc/odata4/tutorials/od4_quick_start_sample.md
index 1c0b1d8..0aed743 100644
--- a/content/doc/odata4/tutorials/od4_quick_start_sample.md
+++ b/content/doc/odata4/tutorials/od4_quick_start_sample.md
@@ -20,7 +20,7 @@ You can now explore the service.
 
 ### Get the war file via the maven repository
 
-To get the war file via the maven repository you can simple look [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~odata-server-sample```) and download the war file. 
+To get the war file via the maven repository you can simple look [here](https://repository.apache.org/index.html#nexus-search;gav~org.apache.olingo~odata-server-sample~~~) and download the war file. 
 
 ### Build the war file on your own