Skip to content

Commit

Permalink
docs: fix typos (#10398)
Browse files Browse the repository at this point in the history
Co-authored-by: Aleksandr Logunov <alex.logunov@near.org>
  • Loading branch information
GoodDaisy and Longarithm committed Jan 15, 2024
1 parent 75d4c60 commit 5c369d4
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/architecture/how/resharding.md
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ The resharding process can be quite resource intensive and affect the regular op
* batch_size - controls the size of batches in which resharding moves data around. Setting a smaller batch size will slow down the resharding process and make it less resource consuming.
* batch_delay - controls the delay between processing of batches. Setting a smaller batch delay will speed up the resharding process and make it more resource consuming.

The remainig fields in the ReshardingConfig are only intended for testing purposes and should remain set to their default values.
The remaining fields in the ReshardingConfig are only intended for testing purposes and should remain set to their default values.

The default configuration for ReshardingConfig should provide a good and safe setting for resharding in the production networks. There is no need for node operators to make any changes to it unless they observe issues.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ and sent it to the block producer at this height ``B1``.

The block producer IS going to add the chunk to the block (as we don't validate
the chunks before adding to blocks - but only when signing the block - see
[Transcations and receipts - last section](./../how/tx_receipts.md)).
[Transactions and receipts - last section](./../how/tx_receipts.md)).

After this block is produced, it is sent to all the validators to get the
signatures.
Expand Down
2 changes: 1 addition & 1 deletion docs/practices/workflows/localnet_on_many_machines.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ rsync -r ~/.near/localnet_multi/node1 192.168.0.2:~/.near/localnet_multi/node1

Now open the config.json file on both machines (node0/config.json on machine1 and node1/config.json on machine2) and:
* for rpc->addr and network->addr:
* Change the addres from 127.0.0.1 to 0.0.0.0 (this means that the port will be accessible from other computers)
* Change the address from 127.0.0.1 to 0.0.0.0 (this means that the port will be accessible from other computers)
* Remember the port numbers (they are generated randomly).
* Also write down the node0's node_key (it is probably: "ed25519:7PGseFbWxvYVgZ89K1uTJKYoKetWs7BJtbyXDzfbAcqX")

Expand Down

0 comments on commit 5c369d4

Please sign in to comment.