summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMagnus Feuer <mfeuer@jaguarlandrover.com>2015-03-09 15:55:14 -0700
committerMagnus Feuer <mfeuer@jaguarlandrover.com>2015-03-09 15:55:14 -0700
commit97922c7ee40120ee9e846cad6a0a002089a0949d (patch)
treec0d63720689f21eca73675aa502235b5269ec2fd
parentd320d2e142d4e75141c67b0d5a72e6df260c9b90 (diff)
downloadrvi_core-97922c7ee40120ee9e846cad6a0a002089a0949d.tar.gz
Updated links
-rw-r--r--README.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.md b/README.md
index b91a7bc..daa0597 100644
--- a/README.md
+++ b/README.md
@@ -12,15 +12,15 @@ choices.
# ADDITIONAL DOCUMENTATION AND RESOURCES#
For a high level description, with an exhaustive master usecase
walkthrough, please see the High Level Design document
-[here](https://wiki2.automotivelinux.org/_media/eg-rvi/15-456-poc-rvi-hld_reva.pdf)
+[here](https://wiki.automotivelinux.org/_media/eg-rvi/15-456-poc-rvi-hld_reva.pdf)
For build instructions, please check the build instructions:
[Markdown](BUILD.md) |
-[PDF](https://wiki2.automotivelinux.org/_media/wiki/wiki/rvi-eg/build.pdf)
+[PDF](https://wiki.automotivelinux.org/_media/eg-rvi/rvi-build.pdf)
For configuration and launch instructions, please check the configuration documentation:
[Markdown](CONFIGURE.md) |
-[PDF](https://wiki2.automotivelinux.org/_media/wiki/wiki/rvi-eg/configure.pdf)
+[PDF](https://wiki.automotivelinux.org/_media/eg-rvi/rvi-configure.pdf)
The RVI mailing list is available at:
[AGL](http://lists.linuxfoundation.org/mailman/listinfo/automotive-eg-rvi)
@@ -124,9 +124,9 @@ own Data Link and Protocol components to handle communication link
management and data encoding / decoding over any media (IP or non-IP).
## ERLANG ##
-[Erlang](www.erlang.org) was chosen to implementation the core
+[Erlang](http://www.erlang.org) was chosen to implementation the core
components of the RVI system. Each component (see the
-[HLD](https://wiki2.automotivelinux.org/_media/15-456-poc-rvi-hld_reva.pdf)
+[HLD](https://wiki.automotivelinux.org/_media/eg-rvi/15-456-poc-rvi-hld_reva.pdf)
for details) run as an erlang application inside a single erlang node.
Several reasons exist for this somewhat unorthodox choice of