From dcaafcd1610c95a44095712515653dd28306c1ed Mon Sep 17 00:00:00 2001 From: Gino Date: Sat, 8 Jun 2024 19:24:27 +0100 Subject: [PATCH] docs(isc-wiki): place block time under block section in jargon.js --- config/jargon.js | 4 ++-- docs/build/isc/v1.1/docs/getting-started/compatibility.md | 4 ++-- .../isc/v1.3-alpha/docs/getting-started/compatibility.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/config/jargon.js b/config/jargon.js index 0e86aecdf95..0144184b203 100644 --- a/config/jargon.js +++ b/config/jargon.js @@ -1,8 +1,6 @@ module.exports = { access: 'The ability to write to the ledger by issuing blocks. In other contexts, it means who has permission to a particular digital asset.', - blocktime: - 'Block Time refers to the average amount of time it takes for a new block to be added to a blockchain. This metric is critical as it determines the network speed and efficiency in processing transactions and maintaining consensus.', accessibility: 'The ease of use and availability of a system or technology for users.', 'accessible Writing': @@ -52,6 +50,8 @@ module.exports = { 'The process of receiving blocks, either created locally by a node or received from a neighbor.', 'block signature': 'Digital signatures attached to blocks to ensure their authenticity.', + 'block time': + 'Block Time refers to the average amount of time it takes for a new block to be added to a blockchain. This metric is critical as it determines the network speed and efficiency in processing transactions and maintaining consensus.', 'block wrapper': 'The block wrapper is additional data around the typical blocks giving important metadata, including the version, time, and block issuer. This metadata allows nodes to follow the right version of the Tangle, to verify the timestamp of blocks, and to identify the creator of each block.', 'blockchain bottleneck': diff --git a/docs/build/isc/v1.1/docs/getting-started/compatibility.md b/docs/build/isc/v1.1/docs/getting-started/compatibility.md index 6bbe83b8df5..9ae8944a138 100644 --- a/docs/build/isc/v1.1/docs/getting-started/compatibility.md +++ b/docs/build/isc/v1.1/docs/getting-started/compatibility.md @@ -33,8 +33,8 @@ Here are some of the most important properties and limitations of EVM support in ### No Enforced Block Time -There is no guaranteed _blocktime_. A new EVM "block" will be created only when an ISC block is created, and ISC does -not enforce an average block time. This means that block times are variable; a new block will be created as soon as needed. +There is no guaranteed _block time_. A new EVM "_block_" will be created only when an ISC block is created, and ISC does +not enforce an average _block time_. This means that block times are variable; a new block will be created as soon as needed. ### The Magic Contract diff --git a/docs/build/isc/v1.3-alpha/docs/getting-started/compatibility.md b/docs/build/isc/v1.3-alpha/docs/getting-started/compatibility.md index 6bbe83b8df5..93bc3859a46 100644 --- a/docs/build/isc/v1.3-alpha/docs/getting-started/compatibility.md +++ b/docs/build/isc/v1.3-alpha/docs/getting-started/compatibility.md @@ -33,8 +33,8 @@ Here are some of the most important properties and limitations of EVM support in ### No Enforced Block Time -There is no guaranteed _blocktime_. A new EVM "block" will be created only when an ISC block is created, and ISC does -not enforce an average block time. This means that block times are variable; a new block will be created as soon as needed. +There is no guaranteed _block time_. A new EVM "block" will be created only when an ISC block is created, and ISC does +not enforce an average _block time_. This means that block times are variable; a new block will be created as soon as needed. ### The Magic Contract