Improve English expressions in documentation

This commit improves awkward or non-native English expressions found
throughout the project documentation to make them more natural for
native English speakers.

Main improvements:
- Remove redundant words ("redundant boilerplate" → "boilerplate")
- Fix superlative constructions ("the most oldest" → "the oldest")
- Improve article usage ("few options" → "a few options")
- Replace awkward phrases ("Special touch for" → "Enhanced")
- Fix grammar patterns ("recommend you to" → "recommend that you")
- Standardize terminology ("the Fediverse" → "the fediverse")
- Remove unnecessary articles ("the most implementations" → "most")
- Fix plural forms ("are a function" → "are functions")
- Improve idiomatic expressions ("first of all" → "first")
- Correct word order ("still is not aware" → "is still not aware")

These changes were made after a comprehensive review of all major
documentation files including README.md, AGENTS.md, CONTRIBUTING.md,
and docs/ directory to identify and correct patterns that would sound
awkward to native English speakers.

[ci skip]

Author: dahlia

AGENTS.md

@@ -12,7 +12,7 @@ Project overview
 
 Fedify is a TypeScript library for building federated server applications
 powered by ActivityPub and related standards, facilitating integration with
-the Fediverse. The project aims to eliminate complexity and boilerplate code
+the fediverse. The project aims to eliminate complexity and boilerplate code
 when implementing federation protocols.
 
 Main features:

CONTRIBUTING.md

@@ -141,7 +141,7 @@ A patch set should include the following:
  -  The *CHANGES.md* entry.  The entry should include the issue number,
     the pull request number, and your name (unless you want to be anonymous).
 
-Bug fix pull requests should target the most oldest maintenance branch that
+Bug fix pull requests should target the oldest maintenance branch that
 the bug affects.  If you are not sure which branch to target, please ask in the
 issue tracker.
 
@@ -400,7 +400,7 @@ code .
 > ~~~~
 
 Note that the `mise run codegen` command is required to run only once at
-very first time, or when you update the code generation scripts.   Otherwise,
+the very first time, or when you update the code generation scripts.  Otherwise,
 you can skip the command and just run:
 
 ~~~~ bash

docs/intro.md

@@ -3,7 +3,7 @@ What is Fedify?
 
 Fedify is a TypeScript library for building federated server apps
 powered by [ActivityPub] and other standards, so-called [fediverse].[^1]
-It aims to eliminate the complexity and redundant boilerplate code when
+It aims to eliminate the complexity and boilerplate code when
 building a federated server app, so that you can focus on your business logic
 and user experience.
 
@@ -16,8 +16,8 @@ Currently, Fedify provides the following features out of the box:
  -  [Object Integrity Proofs][FEP-8b32] & [Linked Data Signatures]
  -  Middlewares for handling webhooks
  -  [NodeInfo] protocol
- -  Special touch for interoperability with Mastodon and few other popular
-    fediverse software
+ -  Enhanced interoperability with Mastodon and other popular fediverse
+    software
  -  [Integration with various web frameworks](./manual/integration.md)
  -  [CLI toolchain for testing and debugging](./cli.md)
 

docs/manual/actor.md

@@ -11,7 +11,7 @@ Actor dispatcher
 In ActivityPub, [actors] are entities that can perform [activities].  You can
 register an actor dispatcher so that Fedify can dispatch an appropriate actor
 by its identifier.  Since the actor dispatcher is the most significant part of
-the Fedify, it is the first thing you need to do to make Fedify work.
+Fedify, it is the first thing you need to do to make Fedify work.
 
 An actor dispatcher is a callback function that takes a `Context` object and
 an identifier, and returns an actor object.  The actor object can be one of
@@ -129,7 +129,7 @@ details.
 Key properties of an `Actor`
 ----------------------------
 
-Despite ActivityPub declares every property of an actor as optional,
+Although ActivityPub declares every property of an actor as optional,
 in practice, you need to set some of them to make the actor work properly
 with the existing ActivityPub implementations.  The following shows
 the key properties of an `Actor` object:
@@ -217,7 +217,7 @@ a `CryptographicKey` instance.  This property is usually used for verifying
 See the [next section](#public-keys-of-an-actor) for details.
 
 > [!TIP]
-> In theory, an actor has multiple `publicKeys`, but in practice, the most
+> In theory, an actor has multiple `publicKeys`, but in practice, most
 > implementations have trouble with multiple keys.  Therefore, it is recommended
 > to set only one key in the `publicKey` property.  Usually, it contains
 > the first RSA-PKCS#1-v1.5 public key of the actor.
@@ -481,7 +481,7 @@ to let users change their WebFinger username without breaking the existing
 network, because changing the WebFinger username does not affect the actor URI.
 
 > [!NOTE]
-> We highly recommend you to set the actor's `preferredUsername` property to
+> We highly recommend that you set the actor's `preferredUsername` property to
 > the corresponding WebFinger username so that peers can find the actor's
 > fediverse handle by fetching the actor object.
 

docs/manual/log.md

@@ -357,7 +357,7 @@ properties:
     the `messageId` property is included in it.  The `messageId` is a unique
     identifier for the background task, which is a UUID.
 
-When you want to trace log messages, first of all you need to use a sink that
+When you want to trace log messages, first you need to use a sink that
 writes log messages as structured data.  For example, you can use
 a [file sink] with a [JSON Lines] formatter.  Oh, and don't forget to set
 `contextLocalStorage` in [`configure()`]!  To sum up, you can configure

docs/tutorial/basics.md

@@ -218,7 +218,7 @@ Now, open your web browser and navigate to <http://localhost:8000/>.  You should
 see the <q>Hello, world</q> message.
 
 As you can guess, [`Deno.serve()`] (in case of Deno), [`Bun.serve()`] (in case
-of Bun), and [`serve()`] (in case of Node.js) are a function to create an HTTP
+of Bun), and [`serve()`] (in case of Node.js) are functions to create an HTTP
 server.  They take a callback function that receives a [`Request`] object and
 returns a [`Response`] object. The `Response` object is sent back to the client.
 
@@ -305,7 +305,7 @@ serve({
 
 :::
 
-The `Federation.fetch()` method takes the incoming `Request` and few options.
+The `Federation.fetch()` method takes the incoming `Request` and a few options.
 In this case, we pass `undefined` as the `contextData` because we don't
 need to share any context data here.
 
@@ -613,7 +613,7 @@ Press ^C to close the tunnel.
 > time you restart the command.
 
 However, since `fedify tunnel` is a reverse proxy between the public internet
-and your server, the server still is not aware the fact that it is exposed to
+and your server, the server is still not aware of the fact that it is exposed to
 the public internet through HTTPS.  In order to make the server aware of it,
 you need to place a [x-forwarded-fetch] middleware in front of the `Federation`.
 
@@ -728,7 +728,7 @@ In ActivityPub, an [inbox] is where an actor receives incoming activities from
 other actors.  To accept follow requests from other servers, we need to register
 an inbox listener for the actor *me*.
 
-Let's register an inbox listener for the actor *me*.  First of all, every
+Let's register an inbox listener for the actor *me*.  First, every
 activity is represented as a class in the Fedify framework.  The `Follow` class
 represents the `Follow` activity.  We will use the `Follow` class to handle
 incoming follow requests:

packages/fedify/README.md

@@ -15,7 +15,7 @@
 
 Fedify is a TypeScript library for building federated server apps
 powered by [ActivityPub] and other standards, so-called [fediverse].[^1]
-It aims to eliminate the complexity and redundant boilerplate code when
+It aims to eliminate the complexity and boilerplate code when
 building a federated server app, so that you can focus on your business logic
 and user experience.
 
@@ -28,8 +28,8 @@ Currently, Fedify provides the following features out of the box:
  -  [Object Integrity Proofs][FEP-8b32] & [Linked Data Signatures]
  -  Middlewares for handling webhooks
  -  [NodeInfo] protocol
- -  Special touch for interoperability with Mastodon and few other popular
-    fediverse software
+ -  Enhanced interoperability with Mastodon and other popular fediverse
+    software
  -  Integration with various web frameworks
  -  CLI toolchain for testing and debugging
 
@@ -89,7 +89,7 @@ Packages
 --------
 
 Fedify is a monorepo that contains several packages, each of which provides
-different features and functionalities.  The main package is *@fedify/fedify*,
+different features.  The main package is *@fedify/fedify*,
 which provides the core functionality of the framework.  Other packages provide
 integrations with various web frameworks, database drivers, and other features.
 Here is the list of packages: