howto/Address-Space.md
... ...
@@ -1,6 +1,6 @@
1 1
DN42 uses network addresses in the [rfc1918](https://tools.ietf.org/html/rfc1918) and [ULA](https://tools.ietf.org/html/rfc4193) ranges. These are described in detail within the sections below.
2 2
3
-The [DN42 registry](https://git.dn42.dev/dn42/registry) is the authoritative source of information on address space assignment. Within the registry, the DN42 address space is divided in to blocks based on _policies_ that define how the addresses may be used. Policies are defined in `inetnum` and `inet6num` objects and can be:
3
+The [DN42 registry](https://git.dn42.dev/dn42/registry) is the authoritative source of information on address space assignment. Within the registry, the DN42 address space is divided into blocks based on _policies_ that define how the addresses may be used. Policies are defined in `inetnum` and `inet6num` objects and can be:
4 4
5 5
- **open** - users may request prefixes in this range, subject to any constraints that are described in the `remark` attributes
6 6
- **closed** - these ranges cannot be assigned
howto/Registry-Authentication.md
... ...
@@ -198,7 +198,7 @@ Use the following to sign the latest `<commit hash>` (that you found using `git
198 198
echo "<commit hash>" | ssh-keygen -Y sign -f <private key file> -n dn42
199 199
```
200 200
201
-Post the signature in to the 'Conversation' section of your pull request to allow the registry maintainers to verify it. It can help to also include the commit hash that you have signed, to avoid any confusion.
201
+Post the signature into the 'Conversation' section of your pull request to allow the registry maintainers to verify it. It can help to also include the commit hash that you have signed, to avoid any confusion.
202 202
203 203
#### Verifying the signature
204 204
... ...
@@ -248,7 +248,7 @@ openssl pkeyutl \
248 248
-in <(echo "<commit hash>") | base64
249 249
```
250 250
251
-Post the signature in to the 'Conversation' section of your pull request to allow the registry maintainers to verify it. It can help to also include the commit hash that you have signed, to avoid any confusion.
251
+Post the signature into the 'Conversation' section of your pull request to allow the registry maintainers to verify it. It can help to also include the commit hash that you have signed, to avoid any confusion.
252 252
253 253
#### Verifying the signature
254 254
... ...
@@ -294,7 +294,7 @@ openssl pkeyutl -sign \
294 294
-in <(echo "<commit hash>") | base64
295 295
```
296 296
297
-Post the signature in to the 'Conversation' section of your pull request to allow the registry maintainers to verify it. It can help to also include the commit hash that you have signed, to avoid any confusion.
297
+Post the signature into the 'Conversation' section of your pull request to allow the registry maintainers to verify it. It can help to also include the commit hash that you have signed, to avoid any confusion.
298 298
299 299
#### Verifying the signature
300 300
internal/ShowAndTell.md
... ...
@@ -5,14 +5,14 @@ Let us know the most creative, best, strangest, complex, wierd or just plain fun
5 5
Document your mad setups in the categories below, with links to a full write up, photos and screenshots welcome.
6 6
7 7
8
-## Things peered in to dn42
9
- - Fun devices peered in to dn42,
8
+## Things peered into dn42
9
+ - Fun devices peered into dn42,
10 10
- Or fun ways to connect them
11
- - The thing must be running BGP and connected in to dn42 as a full dynamic peer
11
+ - The thing must be running BGP and connected into dn42 as a full dynamic peer
12 12
13 13
*Examples*:
14 14
- Fun with virtualisation
15
- - peer in to dn42 from your browser
15
+ - peer into dn42 from your browser
16 16
- Emulate some old bgp capable hardware
17 17
- Fun with hardware
18 18
- obsolete routers you still have in your garage/loft/basement
... ...
@@ -42,7 +42,7 @@ Document your mad setups in the categories below, with links to a full write up,
42 42
***
43 43
44 44
* Retro dn42 access service by Burble
45
- - burble.dn42 provides a [dn42 dialup service](https://dn42.burble.com/retro/) using real modems over VOIP, together with a [modem emulator](https://dn42.burble.com/retro/fake/) to ease attaching retro computers or virtual machines in to dn42
45
+ - burble.dn42 provides a [dn42 dialup service](https://dn42.burble.com/retro/) using real modems over VOIP, together with a [modem emulator](https://dn42.burble.com/retro/fake/) to ease attaching retro computers or virtual machines into dn42
46 46
47 47
- 04dco: At a maximum theoretical speed of a whopping 28.8 Kbps, web browsing and IRC chatting were done. My site still loads faster than everyone else's :)
48 48
services/Original-DNS-(deprecated).md
... ...
@@ -5,7 +5,7 @@ This information is now **deprecated**. Please check [New DNS](/services/New-DNS
5 5
6 6
*(tl;dr)* We have a TLD for dn42, which is `.dn42`. The anycast resolver for `.dn42` runs on `172.20.0.53` and `fd42:d42:d42:54::1`.
7 7
8
-**DNS is build from [whois database](/services/Whois). So please edit your DNS-records there.**
8
+**DNS is built from the [whois database](/services/Whois). Please edit your DNS records there.**
9 9
10 10
## Using the DNS service
11 11
services/Whois.md
... ...
@@ -75,7 +75,7 @@ The Python code for generating the zone from the registry is available on the mo
75 75
76 76
An alternative version to query the registry is it `ip.catgirls.dn42` (IPv6 only) (Source code <https://git.catgirls.systems/famfo/ipinfo>). Note: if there is no `route`/`route6` object for the `inetnum`/`inet6num`, the ip address will not be found.
77 77
78
-This can be used together with `mtr` using the `--ipinfo_provider4` and `--ipinfo_provider6` flags (mtr has to be build from source for that, there hasn't been a release in a while).
78
+This can be used together with `mtr` using the `--ipinfo_provider4` and `--ipinfo_provider6` flags (mtr has to be built from source for that, there hasn't been a release in a while).
79 79
80 80
Example:
81 81
```sh
... ...
@@ -97,7 +97,7 @@ The idea comes from the guys at cymru.com, who provide this service for the Inte
97 97
98 98
# Whois daemons
99 99
100
-We have anycast IPv4 and IPv6, both reachable under whois.dn42. IPs are 172.22.0.43 respective fd42:d42:d42:43::1. Please consider joining these anycast-adresses when you setup your server. Updates every 1 hour would be nice for a start.
100
+We have anycast IPv4 and IPv6, both reachable under whois.dn42. IPs are 172.22.0.43 respective fd42:d42:d42:43::1. Please consider joining these anycast adresses when you set up your server. Updates every 1 hour would be nice for a start.
101 101
102 102
| **person** | **dns** | **ip** |
103 103
|-------------|---------------------------|-----------------|