doc: fix typos and formatting in CONTRIBUTING, i2p, bitcoin-conf, files
What changed, and why it matters
This commit fixes four minor typos and spacing issues in documentation files only. There are no code changes and no security implications.
No security action needed. Treat as a normal documentation cleanup commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit is a pure documentation patch touching four markdown files: CONTRIBUTING.md, doc/i2p.md, doc/bitcoin-conf.md, and doc/files.md. Changes are limited to grammar corrections (‘Valid areas as’ → ‘Valid areas are’), removal of a double space, a duplicated word (‘some negating some lists’ → ‘some negating lists’), and a missing comma space. No source code, build scripts, tests, or configuration logic were modified.
Changed components
CONTRIBUTING.mddoc/i2p.mddoc/bitcoin-conf.mddoc/files.mdInspect captured patch +4 / −4
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index deb2b40a..f0e88514 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -146,7 +146,7 @@ about Git.
### Creating the Pull Request
The title of the pull request should be prefixed by the component or area that
-the pull request affects. Valid areas as:
+the pull request affects. Valid areas are:
- `consensus` for changes to consensus critical code
- `doc` for changes to the documentation
diff --git a/doc/bitcoin-conf.md b/doc/bitcoin-conf.md
index daa7fcba..e768961d 100644
--- a/doc/bitcoin-conf.md
+++ b/doc/bitcoin-conf.md
@@ -65,7 +65,7 @@ Almost all options can be negated by being specified with a `no` prefix. For exa
In general, negating an option is like setting it to `0` if it is a boolean or integer option, and setting it to an empty string or path or list if it is a string or path or list option.
-However, there are exceptions to this general rule. For example, it is an error to negate some options (e.g. `-nodatadir` is disallowed), and some negated strings are treated like `"0"` instead of `""` (e.g. `-noproxy` is treated like `-proxy=0`), and some negating some lists can have side effects in addition to clearing the lists (e.g. `-noconnect` disables automatic connections in addition to dropping any manual connections specified previously with `-connect=<host>`). When there are exceptions to the rule, they should either be obvious from context, or should be mentioned in usage documentation. Nonobvious, undocumented exceptions should be reported as bugs.
+However, there are exceptions to this general rule. For example, it is an error to negate some options (e.g. `-nodatadir` is disallowed), and some negated strings are treated like `"0"` instead of `""` (e.g. `-noproxy` is treated like `-proxy=0`), and some negating lists can have side effects in addition to clearing the lists (e.g. `-noconnect` disables automatic connections in addition to dropping any manual connections specified previously with `-connect=<host>`). When there are exceptions to the rule, they should either be obvious from context, or should be mentioned in usage documentation. Nonobvious, undocumented exceptions should be reported as bugs.
## Configuration File Path
diff --git a/doc/files.md b/doc/files.md
index 8a11e089..e8f28692 100644
--- a/doc/files.md
+++ b/doc/files.md
@@ -165,5 +165,5 @@ This table describes the files installed by Bitcoin Core across different platfo
## Filesystem recommendations
-When choosing a filesystem for the data directory (`datadir`) or blocks directory (`blocksdir`) on **macOS**,the `exFAT` filesystem should be avoided.
+When choosing a filesystem for the data directory (`datadir`) or blocks directory (`blocksdir`) on **macOS**, the `exFAT` filesystem should be avoided.
There have been multiple reports of database corruption and data loss when using this filesystem with Bitcoin Core, see [Issue #31454](https://github.com/bitcoin/bitcoin/issues/31454) for more details.
diff --git a/doc/i2p.md b/doc/i2p.md
index 624b651f..2877c1e5 100644
--- a/doc/i2p.md
+++ b/doc/i2p.md
@@ -86,7 +86,7 @@ address is used for making outbound connections and accepting inbound
connections.
In the I2P network, the receiver of an inbound connection sees the address of
-the initiator. This is unlike the Tor network, where the recipient does not
+the initiator. This is unlike the Tor network, where the recipient does not
know who is connecting to it.
If your node is configured by setting `-i2pacceptincoming=0` to not accept
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.