Commit

Author:

Hash:

Timestamp:

+11 -8 +/-5 browse

Kevin Schoon [me@kevinschoon.com]

8b34b591c37fe7ef6e40d3dd900e5df468e6eda1

Tue, 25 Aug 2026 19:33:38 +0000 (5 days ago)

add spelling fixes
1diff --git a/check.sh b/check.sh
2new file mode 100755
3index 0000000..ade1d1c
4--- /dev/null
5+++ b/check.sh
6 @@ -0,0 +1,3 @@
7+ #!/bin/sh
8+
9+ find content -type f -name '*.md' -exec aspell check {} \;
10 diff --git a/content/_index.md b/content/_index.md
11index 677a170..e3adb6e 100644
12--- a/content/_index.md
13+++ b/content/_index.md
14 @@ -12,8 +12,8 @@ implemented can enhance interoperability and content discovery of different
15 across the internet. You can validate an existing ForgeFeed implementation
16 by navigating to the [validator](/validator) page.
17
18- NOTE that all specifications provided below MAY be implemented indepedenantly
19- at the descrescion of the developer however it is a recommended that a server
20+ NOTE that all specifications provided below MAY be implemented independently
21+ at the discretion of the developer however it is a recommended that a server
22 implement them all for maximum effect.
23
24 # Specifications
25 diff --git a/content/project-atom-feed.md b/content/project-atom-feed.md
26index d1ffc3c..bc0f6da 100644
27--- a/content/project-atom-feed.md
28+++ b/content/project-atom-feed.md
29 @@ -8,7 +8,7 @@ A forge SHOULD expose an [Atom](https://www.rfc-editor.org/rfc/rfc4287)
30 feed in order for other peers to subscribe to interesting code projects that
31 are developed on your forge. The server SHOULD expose projects ordered by those
32 which have been recently updated. The heuristic used to determine what has
33- been updated depends on the implementor forge. A common way to do this may be
34+ been updated depends on the implementer forge. A common way to do this may be
35 to simply look at your VCS's concept of a commit and order updates with that.
36
37 ## Determine if a Host Supports Forge Feed
38 @@ -100,7 +100,7 @@ already have cached versions of your project data.
39
40 ### Recommendations for Enumerating Project Events
41
42- #### Specify a Maximum Timeframe
43+ #### Specify a Maximum Time-frame
44
45 Your activity feed should not include project events that are older than 1
46 week.
47 diff --git a/content/webfinger-project.md b/content/webfinger-project.md
48index 6eba516..3c3ca7f 100644
49--- a/content/webfinger-project.md
50+++ b/content/webfinger-project.md
51 @@ -2,8 +2,8 @@
52 title: Project Discovery via WebFinger
53 ---
54
55- A project refers to a peice of software which may be spread across multiple
56- code [repositories](/webfinger-repository). For example a consider a fictious
57+ A project refers to a piece of software which may be spread across multiple
58+ code [repositories](/webfinger-repository). For example a consider a fictitious
59 programming language which may be composed of several components such as a
60 compiler, a standard library, example codebases, a marketing website, etc.
61 When the architecture of such a project spans multiple repositories then it
62 @@ -50,7 +50,7 @@ https://example.org/.well-known/webfinger?resource=project://spartacus@example.o
63 ## Parsing
64
65 An example parser written in the Python programming language. Any programming
66- language which implements a valid RFC7565 parser should be sufficent for
67+ language which implements a valid RFC7565 parser should be sufficient for
68 reading a project URI.
69
70 ```python
71 diff --git a/content/webfinger-repository.md b/content/webfinger-repository.md
72index f1cc33e..8387b61 100644
73--- a/content/webfinger-repository.md
74+++ b/content/webfinger-repository.md
75 @@ -41,7 +41,7 @@ https://example.org/.well-known/webfinger?resource=repository://spartacus/game@e
76 ## Parsing
77
78 An example parser written in the Python programming language. Any programming
79- language which implements a valid RFC7565 parser should be sufficent for
80+ language which implements a valid RFC7565 parser should be sufficient for
81 reading a project URI.
82
83 ```python