[doc] Fix broken links in the documentation
Signed-off-by: Jorge Prendes <jprendes@lowrisc.org>
Signed-off-by: Jorge Prendes <jorge.prendes@gmail.com>
diff --git a/hw/ip/keymgr/doc/dv/index.md b/hw/ip/keymgr/doc/dv/index.md
index 238a7d8..9558488 100644
--- a/hw/ip/keymgr/doc/dv/index.md
+++ b/hw/ip/keymgr/doc/dv/index.md
@@ -57,7 +57,7 @@
This agent will return random data as entropy when the KEYMGR sends a request.
### KMAC_APP Agent
-The KEYMGR testbench instantiates a [`kmac_app_agent`](<{{ relref "hw/dv/sv/kmac_app_agent/README.md" >}}) to request a KMAC hash operation on the secret data.
+The KEYMGR testbench instantiates a [`kmac_app_agent`]({{< relref "hw/dv/sv/kmac_app_agent/README.md" >}}) to request a KMAC hash operation on the secret data.
### UVM RAL Model
The KEYMGR RAL model is created with the [`ralgen`]({{< relref "hw/dv/tools/ralgen/README.md" >}}) FuseSoC generator script automatically when the simulation is at the build stage.
diff --git a/hw/ip/kmac/doc/dv/index.md b/hw/ip/kmac/doc/dv/index.md
index bc588f7..dc783b7 100644
--- a/hw/ip/kmac/doc/dv/index.md
+++ b/hw/ip/kmac/doc/dv/index.md
@@ -93,7 +93,7 @@
This agent will return random data as entropy after a random delay any time the KMAC sends a request.
### KMAC_APP Agent
-The KMAC testbench instantiates an array of [`kmac_app_agent`](<{{ relref "hw/dv/sv/kmac_app_agent/README.md" >}}) to model the application interfaces used by other IP blocks to request a KMAC hash operation on some data.
+The KMAC testbench instantiates an array of [`kmac_app_agent`]({{< relref "hw/dv/sv/kmac_app_agent/README.md" >}}) to model the application interfaces used by other IP blocks to request a KMAC hash operation on some data.
These interfaces are used to send in message data to the KMAC, and to receive an output digest.
### UVM RAL Model
@@ -102,7 +102,7 @@
It can be created manually by invoking [`regtool`]({{< relref "util/reggen/README.md" >}}):
### Reference models
-The KMAC testbench utilizes a [C++ reference model](<{{ relref "hw/ip/dv/kmac/dpi/vendor/kerukuro_digestpp/README.md" >}}) for various hashing operations (SHA3, SHAKE, CSHAKE, KMAC) to check the DUT's digest output for correctness.
+The KMAC testbench utilizes a [C++ reference model]({{< relref "hw/ip/kmac/dv/dpi/vendor/kerukuro_digestpp/README.md" >}}) for various hashing operations (SHA3, SHAKE, CSHAKE, KMAC) to check the DUT's digest output for correctness.
### Stimulus strategy
#### Test sequences
diff --git a/sw/README.md b/sw/README.md
index 102d15c..4787cb9 100644
--- a/sw/README.md
+++ b/sw/README.md
@@ -12,7 +12,7 @@
$ ninja -C build-out sw/device/examples/hello_world/hello_world_export_fpga_nexysvideo
```
-The resulting binaries will be located at `build-bin/sw/device/examples/hello_world`. For more information, check out [the relevant User Guide](../doc/ug/getting_started_sw.md).
+The resulting binaries will be located at `build-bin/sw/device/examples/hello_world`. For more information, check out [the relevant User Guide]({{< relref "../doc/ug/getting_started_build_sw.md" >}}).
The location of the RISC-V toolchain is /tools/riscv by default.
If your toolchain is located elsewhere set the `TOOLCHAIN_PATH` to that path before running `meson_init.sh`
diff --git a/sw/_index.md b/sw/_index.md
index 68bc772..b9322f3 100644
--- a/sw/_index.md
+++ b/sw/_index.md
@@ -58,7 +58,7 @@
All DIFs are also documented on their respective [Hardware IP Specification]({{< relref "hw" >}})
-## Vendored in Code see [Vendor Tool User Guide]({{< relref "doc/ug/vendor_hw.md" >}})
+## Vendored in Code see [Vendor Tool User Guide]({{% relref "doc/ug/vendor_hw.md" %}})
* [CoreMark](https://github.com/eembc/coremark)
* [RISC-V Compliance](https://github.com/riscv/riscv-compliance)
