aboutsummaryrefslogtreecommitdiff
path: root/content
diff options
context:
space:
mode:
authorDimitri Staessens <dimitri@ouroboros.rocks>2020-01-21 20:27:42 +0100
committerDimitri Staessens <dimitri@ouroboros.rocks>2020-01-21 20:27:42 +0100
commit390cc2153d05f8d53be1d80a472f6495aec92653 (patch)
tree69e1cff1fb840437fd249a102fd256ae09dfbdd4 /content
parent5fe0b5aa2a490c0ef6419f709543be6efd57a16d (diff)
downloadwebsite-390cc2153d05f8d53be1d80a472f6495aec92653.tar.gz
website-390cc2153d05f8d53be1d80a472f6495aec92653.zip
content: Overview link to fa and datapath sections
Diffstat (limited to 'content')
-rw-r--r--content/en/docs/Overview/_index.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/content/en/docs/Overview/_index.md b/content/en/docs/Overview/_index.md
index 33f6333..455cf2b 100644
--- a/content/en/docs/Overview/_index.md
+++ b/content/en/docs/Overview/_index.md
@@ -36,4 +36,9 @@ The Ouroboros daemons can be thought of as **software routers** that
can be connected to each other. Each one has an address,
and they forward packets among each other. The daemons also implement
a Distributed Hash Table, so the network has its own internal
- name-to-address resolution. \ No newline at end of file
+ name-to-address resolution.
+
+The best place to start understanding a bit what this does and how it
+differs from other packet networks is to have a quick look at the
+[flow allocation](/docs/concepts/fa/) and [data
+path](/docs/concepts/datapath/) sections.