summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWim Taymans <wtaymans@redhat.com>2020-06-11 16:30:27 +0200
committerWim Taymans <wtaymans@redhat.com>2020-06-11 16:30:27 +0200
commit00ca566b1809a0b9fe115a62db1d1d6aa52fc067 (patch)
tree10fdbedcd37e9a8b473ab0342912b771eed806cf /doc
parent9b245da5c07aea4d64caebcd140a66853b823b0e (diff)
doc: cleanups
Diffstat (limited to 'doc')
-rw-r--r--doc/tutorial1.md4
-rw-r--r--doc/tutorial2.md4
-rw-r--r--doc/tutorial3.md8
3 files changed, 7 insertions, 9 deletions
diff --git a/doc/tutorial1.md b/doc/tutorial1.md
index 1e952299..a576cec6 100644
--- a/doc/tutorial1.md
+++ b/doc/tutorial1.md
@@ -1,4 +1,4 @@
-[index](tutorial-index.md) [next](tutorial2.md)
+[[index](tutorial-index.md) [[next]](tutorial2.md)
# Getting started (Tutorial 1)
@@ -45,4 +45,4 @@ Linked with libpipewire 0.3.5
#
```
-[index](tutorial-index.md) [next](tutorial2.md)
+[[index](tutorial-index.md) [[next]](tutorial2.md)
diff --git a/doc/tutorial2.md b/doc/tutorial2.md
index 9ec01a60..65f90caa 100644
--- a/doc/tutorial2.md
+++ b/doc/tutorial2.md
@@ -1,4 +1,4 @@
-[previous](tutorial1.md) [index](tutorial-index.md) [next](tutorial3.md)
+[[previous]](tutorial1.md) [[index](tutorial-index.md) [[next]](tutorial3.md)
# Enumerating objects (Tutorial 2)
@@ -177,4 +177,4 @@ continue forever. In the next tutorial we'll see how we can nicely
exit our application after we received all server objects.
-[previous](tutorial1.md) [index](tutorial-index.md) [next](tutorial3.md)
+[[previous]](tutorial1.md) [[index](tutorial-index.md) [[next]](tutorial3.md)
diff --git a/doc/tutorial3.md b/doc/tutorial3.md
index 6263cd62..1f6bce03 100644
--- a/doc/tutorial3.md
+++ b/doc/tutorial3.md
@@ -1,4 +1,4 @@
-[previous](tutorial2.md) [index](tutorial-index.md) [next](tutorial4.md)
+[[previous]](tutorial2.md) [[index](tutorial-index.md) [[next]](tutorial4.md)
# Forcing a roundtrip (Tutorial 3)
@@ -85,7 +85,7 @@ This triggers the `sync` method on the core object with id
Because this is a method on a proxy object, it will be executed
asynchronously and the returns value will reflect this. PipeWire
uses the return values of the underlying SPA (Simple Plugin API)
-helper objects (See also [error codes](spa/design.md#error-codes).
+helper objects (See also [error codes](spa/design.md#error-codes)).
Because all messages on the PipeWire server are handled sequencially,
the sync method will be executed after all previous methods are
@@ -109,8 +109,6 @@ remove the listener:
```c
spa_hook_remove(&core_listener);
- return 0;
-}
```
If we add this roundtrip method to our code and call it instead of the
@@ -207,4 +205,4 @@ use:
gcc -Wall tutorial3.c -o tutorial3 $(pkg-config --cflags --libs libpipewire-0.3)
```
-[previous](tutorial2.md) [index](tutorial-index.md) [next](tutorial4.md)
+[[previous]](tutorial2.md) [[index](tutorial-index.md) [[next]](tutorial4.md)