mirror of
https://github.com/dashpay/dash.git
synced 2024-12-25 03:52:49 +01:00
Merge #12283: Fix typos
1340eda3b7
Fix typos (practicalswift)
Pull request description:
Fix typos.
Tree-SHA512: 533a136831387ef26e9a74ba078437496bee38cc026da73fa9e6f6e7f4d5665eccac24cf3ef05e6d3af1329a1214f5ce71b039ddb8378b074e6d4408b8701f95
This commit is contained in:
parent
ab5aeed920
commit
0d4d3c3254
@ -368,7 +368,7 @@ public:
|
||||
|
||||
// Note that of those which support the service bits prefix, most only support a subset of
|
||||
// possible options.
|
||||
// This is fine at runtime as we'll fall back to using them as a oneshot if they dont support the
|
||||
// This is fine at runtime as we'll fall back to using them as a oneshot if they don't support the
|
||||
// service bits we want, but we should get them updated to support all service bits wanted by any
|
||||
// release ASAP to avoid it where possible.
|
||||
vSeeds.emplace_back("dnsseed.dash.org");
|
||||
|
@ -325,7 +325,7 @@ enum ServiceFlags : uint64_t {
|
||||
* Thus, generally, avoid calling with peerServices == NODE_NONE, unless
|
||||
* state-specific flags must absolutely be avoided. When called with
|
||||
* peerServices == NODE_NONE, the returned desirable service flags are
|
||||
* guaranteed to not change dependant on state - ie they are suitable for
|
||||
* guaranteed to not change dependent on state - ie they are suitable for
|
||||
* use when describing peers which we know to be desirable, but for which
|
||||
* we do not have a confirmed set of service flags.
|
||||
*
|
||||
|
Loading…
Reference in New Issue
Block a user