diff options
| author | John Bampton <jbampton@users.noreply.github.com> | 2024-05-01 06:54:05 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-30 16:54:05 -0400 |
| commit | f61885edcf5e63ac205b1ca5f08173f1336bff74 (patch) | |
| tree | 2d577255ee2fd3c3c5743edf1c0184a67abcb7d2 /bip-0014.mediawiki | |
| parent | 2d9e431fbe654640b55bca3bf8c4b17462890109 (diff) | |
docs: fix spelling (#1117)
Co-authored-by: Mark "Murch" Erhardt <murch@murch.one>
Diffstat (limited to 'bip-0014.mediawiki')
| -rw-r--r-- | bip-0014.mediawiki | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0014.mediawiki b/bip-0014.mediawiki index abd575c..fded420 100644 --- a/bip-0014.mediawiki +++ b/bip-0014.mediawiki @@ -28,7 +28,7 @@ Version bumping can also introduce incompatibilities and fracture the network. I By using a protocol version, we set all implementations on the network to a common standard. Everybody is able to agree within their confines what is protocol and what is implementation-dependent. A user agent string is offered as a 'vanity-plate' for clients to distinguish themselves in the network. -Separation of the network protocol from the implemention, and forming development of said protocol by means of a mutual consensus among participants, has the democratic disadvantage when agreement is hard to reach on contentious issues. To mitigate this issue, strong communication channels and fast release schedules are needed, and are outside the scope of this document (concerning a process-BIP type). +Separation of the network protocol from the implementation, and forming development of said protocol by means of a mutual consensus among participants, has the democratic disadvantage when agreement is hard to reach on contentious issues. To mitigate this issue, strong communication channels and fast release schedules are needed, and are outside the scope of this document (concerning a process-BIP type). User agents provide extra tracking information that is useful for keeping tabs on network data such as client implementations used or common architectures/operating-systems. In the rare case they may even provide an emergency method of shunning faulty clients that threaten network health- although this is strongly unrecommended and extremely bad form. The user agent does not provide a method for clients to work around and behave differently to different implementations, as this will lead to protocol fracturing. |