howto/OpenBGPD.md
... ...
@@ -40,7 +40,7 @@ network prefix-set mynetworks set large-community $ASN:1:1
40 40
41 41
## neighbors
42 42
For each neighbor its ASN and transfer ULA is required.
43
-An optional description is provided such that [`bgpctl`](http://man.openbsd.org/bgpctl.8) for example can be used with mnemonic names instead of AS numbers:
43
+An optional description is provided such that [**bgpctl(8)**](http://man.openbsd.org/bgpctl.8) for example can be used with mnemonic names instead of AS numbers:
44 44
```
45 45
# peer A, transport over IPSec/GRE
46 46
$A-local="fd00:12:34:A::1"
... ...
@@ -109,7 +109,7 @@ match from AS $A-ASN set { nexthop $A-remote }
109 109
OpenBSD ships with [**rpki-client(8)**](http://man.openbsd.org/rpki-client.8) which nicely integrates with **bgpd**.
110 110
Since DN42 emulates an IRR WHOIS service through the registry repository instead of providing an RPKI repository, this cool cannot be used.
111 111
112
-Instead, a shell script parses route objects from the registry repository and generates a `roa-set { ... }` block that is to be included in the main configuration file.
112
+Instead, a shell script parses route objects from the registry repository and generates a `roa-set {...}` block that is to be included in the main configuration file.
113 113
114 114
One single `roa-set` may be defined, against which **bgpd** will validate the origin of each prefix; this allows filter rules to use the `ovs` keyword as demonstrated above.
115 115