Hyperledger Besu -> Besu (#1684)

Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com> Signed-off-by: Joan E <153745173+joaniefromtheblock@users.noreply.github.com>
hyperledger · Sep 19, 2024 · e4cb2a2 · e4cb2a2
1 parent f7922cc
commit e4cb2a2
Show file tree

Hide file tree

Showing 87 changed files with 160 additions and 160 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -1,2 +1,2 @@
-For changes see the Hyperledger Besu
+For changes see the Besu
 [CHANGELOG.md](https://github.com/hyperledger/besu/blob/master/CHANGELOG.md)
diff --git a/docs/private-networks/concepts/permissioning/plugin.md b/docs/private-networks/concepts/permissioning/plugin.md
@@ -8,7 +8,7 @@ tags:
 
 # Permissioning plugin
 
-You can define complex [permissioning](index.md) solutions by building a plugin that extends Hyperledger Besu functionality.
+You can define complex [permissioning](index.md) solutions by building a plugin that extends Besu functionality.
 
 The plugin API provides a `PermissioningService` interface that currently supports connection permissioning and message permissioning.
 

diff --git a/docs/private-networks/concepts/pki.md b/docs/private-networks/concepts/pki.md
@@ -14,7 +14,7 @@ Public key infrastructure (PKI) support is an early access feature, and function
 
 :::
 
-Hyperledger Besu's public key infrastructure allows you to use certificates issued by a trusted authority to manage node and account identities in the following ways:
+Besu's public key infrastructure allows you to use certificates issued by a trusted authority to manage node and account identities in the following ways:
 
 - Node permissioning - Only authorized nodes can connect to other nodes in the network using TLS for the P2P communication.
 - Block proposal permissioning - Only blocks proposed by authorized validators are accepted.

diff --git a/docs/private-networks/concepts/plugins.md b/docs/private-networks/concepts/plugins.md
@@ -8,7 +8,7 @@ tags:
 
 # Plugins
 
-You can extend Hyperledger Besu functionality by building Java plugins or using existing open source Besu plugins. Use the Plugin API to take data from any Besu network, public or permissioned, and feed it into an application or system.
+You can extend Besu functionality by building Java plugins or using existing open source Besu plugins. Use the Plugin API to take data from any Besu network, public or permissioned, and feed it into an application or system.
 
 For example, create a plugin to add more monitoring functionality or stream event data to a third-party application. The API exposes data about the following components:
 

diff --git a/docs/private-networks/concepts/privacy/plugin.md b/docs/private-networks/concepts/privacy/plugin.md
@@ -6,7 +6,7 @@ sidebar_position: 5
 
 # Privacy plugin
 
-You can define your own strategy for private transactions by building a plugin that extends Hyperledger Besu functionality.
+You can define your own strategy for private transactions by building a plugin that extends Besu functionality.
 
 The plugin can take many forms, but it must provide Besu with a private transaction when required.
 

diff --git a/docs/private-networks/get-started/install/binary-distribution.md b/docs/private-networks/get-started/install/binary-distribution.md
@@ -1,6 +1,6 @@
 ---
 title: Install binary distribution
-description: Install or upgrade Hyperledger Besu from binary distribution
+description: Install or upgrade Besu from binary distribution
 sidebar_position: 3
 tags:
   - private networks
@@ -17,7 +17,7 @@ tags:
 
 :::caution
 
-Hyperledger Besu supports:
+Besu supports:
 
 - MacOS High Sierra 10.13 or later versions.
 - Java 21+. You can install Java using `brew install openjdk@21`. Alternatively, you can manually install the [Java JDK](https://www.oracle.com/java/technologies/downloads).

diff --git a/docs/private-networks/get-started/install/index.md b/docs/private-networks/get-started/install/index.md
@@ -1,6 +1,6 @@
 ---
 title: Installation options
-description: Options for getting started with Hyperledger Besu
+description: Options for getting started with Besu
 sidebar_position: 1
 tags:
   - private networks
@@ -17,12 +17,12 @@ You can also install the following:
 
 ## Build from source
 
-If you want to use the latest development version of Hyperledger Besu or a specific commit, build from source. Otherwise, use the [binary] or [Docker image] for more stable versions.
+If you want to use the latest development version of Besu or a specific commit, build from source. Otherwise, use the [binary] or [Docker image] for more stable versions.
 
-View the [Hyperledger Wiki] for instructions to install Hyperledger Besu from source.
+View the [Wiki] for instructions to install Besu from source.
 
 <!-- link -->
 
-[Hyperledger Wiki]: https://wiki.hyperledger.org/display/BESU/Building+from+source
+[Wiki]: https://wiki.hyperledger.org/display/BESU/Building+from+source
 [binary]: binary-distribution.md
 [Docker image]: run-docker-image.md
diff --git a/docs/private-networks/get-started/install/run-docker-image.md b/docs/private-networks/get-started/install/run-docker-image.md
@@ -1,14 +1,14 @@
 ---
 title: Run Besu from Docker image
-description: Run Hyperledger Besu using the official docker image
+description: Run Besu using the official docker image
 sidebar_position: 2
 tags:
   - private networks
 ---
 
 # Run Besu from a Docker image
 
-Hyperledger Besu provides a Docker image to run a Besu node in a Docker container.
+Besu provides a Docker image to run a Besu node in a Docker container.
 
 Use this Docker image to run a single Besu node without installing Besu.
 

diff --git a/docs/private-networks/how-to/configure/bootnodes.md b/docs/private-networks/how-to/configure/bootnodes.md
@@ -24,7 +24,7 @@ To find peers, configure one or more bootnodes. To configure a specific set of p
 
 :::note Mainnet and public testnets
 
-For Mainnet and the Sepolia and Holesky testnets, Hyperledger Besu has an internal list of enode URLs and uses this list automatically when you specify the [`--network`](../../../public-networks/reference/cli/options.md#network) option.
+For Mainnet and the Sepolia and Holesky testnets, Besu has an internal list of enode URLs and uses this list automatically when you specify the [`--network`](../../../public-networks/reference/cli/options.md#network) option.
 
 :::
 

diff --git a/docs/private-networks/how-to/configure/consensus/clique.md b/docs/private-networks/how-to/configure/consensus/clique.md
@@ -1,6 +1,6 @@
 ---
 title: Clique
-description: Hyperledger Besu Clique Proof-of-Authority (PoA) consensus protocol implementation
+description: Besu Clique Proof-of-Authority (PoA) consensus protocol implementation
 sidebar_position: 4
 path: blob/master/config/src/main/resources/
 source: rinkeby.json

diff --git a/docs/private-networks/how-to/configure/consensus/ibft.md b/docs/private-networks/how-to/configure/consensus/ibft.md
@@ -1,6 +1,6 @@
 ---
 title: IBFT 2.0
-description: Hyperledger Besu IBFT 2.0 proof of authority (PoA) consensus protocol implementation
+description: Besu IBFT 2.0 proof of authority (PoA) consensus protocol implementation
 sidebar_position: 3
 tags:
   - private networks

diff --git a/docs/private-networks/how-to/configure/consensus/qbft.md b/docs/private-networks/how-to/configure/consensus/qbft.md
@@ -1,6 +1,6 @@
 ---
 title: QBFT
-description: Hyperledger Besu QBFT proof of authority (PoA) consensus protocol implementation
+description: Besu QBFT proof of authority (PoA) consensus protocol implementation
 sidebar_position: 2
 tags:
   - private networks
@@ -11,7 +11,7 @@ import TabItem from '@theme/TabItem';
 
 # Configure QBFT consensus
 
-Hyperledger Besu implements the QBFT proof of authority (PoA) [consensus protocol](index.md). QBFT is the recommended enterprise-grade consensus protocol for private networks.
+Besu implements the QBFT proof of authority (PoA) [consensus protocol](index.md). QBFT is the recommended enterprise-grade consensus protocol for private networks.
 
 In QBFT networks, approved accounts, known as validators, validate transactions and blocks. Validators take turns to create the next block. Before inserting the block onto the chain, a super-majority (greater than or equal to 2/3) of validators must first sign the block.
 

diff --git a/docs/private-networks/how-to/configure/tls/client-and-server.md b/docs/private-networks/how-to/configure/tls/client-and-server.md
@@ -7,7 +7,7 @@ tags:
 
 # Configure client and server TLS
 
-Hyperledger Besu supports TLS for client and server communication. For example, you can configure TLS for communication between [Web3Signer](https://docs.web3signer.consensys.net/concepts/tls) and Besu, and Besu and [Tessera](https://docs.tessera.consensys.net/HowTo/Configure/TLS/).
+Besu supports TLS for client and server communication. For example, you can configure TLS for communication between [Web3Signer](https://docs.web3signer.consensys.net/concepts/tls) and Besu, and Besu and [Tessera](https://docs.tessera.consensys.net/HowTo/Configure/TLS/).
 
 The following diagram displays an example client and server TLS configuration.
 

diff --git a/docs/private-networks/how-to/deploy/ansible.md b/docs/private-networks/how-to/deploy/ansible.md
@@ -1,14 +1,14 @@
 ---
 sidebar_position: 2
 title: Use Ansible
-description: Deploying Hyperledger Besu with Ansible role on Galaxy
+description: Deploying Besu with Ansible role on Galaxy
 tags:
   - private networks
 ---
 
 # Deploy Besu with Ansible
 
-To deploy Besu using Ansible, use the [Hyperledger Besu role](https://galaxy.ansible.com/consensys/hyperledger_besu) published on Galaxy.
+To deploy Besu using Ansible, use the [Besu role](https://galaxy.ansible.com/consensys/hyperledger_besu) published on Galaxy.
 
 For more information, see the "Read Me" button on the [Ansible Galaxy Besu page](https://galaxy.ansible.com/consensys/hyperledger_besu).
 

diff --git a/docs/private-networks/how-to/deploy/kubernetes.md b/docs/private-networks/how-to/deploy/kubernetes.md
@@ -1,7 +1,7 @@
 ---
 sidebar_position: 3
 title: Use Kubernetes
-description: Deploying Hyperledger Besu with Kubernetes
+description: Deploying Besu with Kubernetes
 tags:
   - private networks
 ---

diff --git a/docs/private-networks/how-to/monitor/elastic-stack.md b/docs/private-networks/how-to/monitor/elastic-stack.md
@@ -1,7 +1,7 @@
 ---
 title: Use Elastic Stack
 sidebar_position: 3
-description: Using Elastic Stack (ELK) with Hyperledger Besu
+description: Using Elastic Stack (ELK) with Besu
 tags:
   - private networks
 ---

diff --git a/docs/private-networks/how-to/monitor/index.md b/docs/private-networks/how-to/monitor/index.md
@@ -17,4 +17,4 @@ You can also use the following monitoring tools in private networks:
 - [OpenTelemetry](opentelemetry.md)
 - [Chainlens Explorer](chainlens.md)
 
-For an overview of monitoring Hyperledger Besu, view [this recording](https://www.youtube.com/watch?v=7BuutRe0I28&feature=youtu.be).
+For an overview of monitoring Besu, view [this recording](https://www.youtube.com/watch?v=7BuutRe0I28&feature=youtu.be).
diff --git a/docs/private-networks/how-to/monitor/loki.md b/docs/private-networks/how-to/monitor/loki.md
@@ -1,7 +1,7 @@
 ---
 title: Use Grafana Loki
 sidebar_position: 2
-description: Using Grafana Loki log management platform with Hyperledger Besu
+description: Using Grafana Loki log management platform with Besu
 tags:
   - private networks
 ---

diff --git a/docs/private-networks/how-to/monitor/opentelemetry.md b/docs/private-networks/how-to/monitor/opentelemetry.md
@@ -11,13 +11,13 @@ import TabItem from '@theme/TabItem';
 
 # Use OpenTelemetry
 
-You can use the OpenTelemetry monitoring and tracing service to gather node metrics and traces. To enable OpenTelemetry to access Hyperledger Besu, use the [`--metrics-enabled`](../../../public-networks/reference/cli/options.md#metrics-enabled) and [`--metrics-protocol=opentelemetry`](../../../public-networks/reference/cli/options.md#metrics-protocol) options. Use [Splunk](https://splunk.com) to visualize the collected data. A [Besu Sync example](https://github.com/splunk/splunk-connect-for-ethereum/tree/master/examples/besu-sync) is available.
+You can use the OpenTelemetry monitoring and tracing service to gather node metrics and traces. To enable OpenTelemetry to access Besu, use the [`--metrics-enabled`](../../../public-networks/reference/cli/options.md#metrics-enabled) and [`--metrics-protocol=opentelemetry`](../../../public-networks/reference/cli/options.md#metrics-protocol) options. Use [Splunk](https://splunk.com) to visualize the collected data. A [Besu Sync example](https://github.com/splunk/splunk-connect-for-ethereum/tree/master/examples/besu-sync) is available.
 
 :::tip
 
 Use OpenTelemetry to monitor the sync time of your Besu node and show where time is spent internally and over the JSON-RPC interface.
 
-[This office hours recording](https://wiki.hyperledger.org/display/BESU/2021-01-19+Office+Hours+Notes) shows examples of monitoring Hyperledger Besu.
+[This office hours recording](https://wiki.hyperledger.org/display/BESU/2021-01-19+Office+Hours+Notes) shows examples of monitoring Besu.
 
 :::
 

diff --git a/docs/private-networks/how-to/monitor/quorum-hibernate.md b/docs/private-networks/how-to/monitor/quorum-hibernate.md
@@ -1,7 +1,7 @@
 ---
 title: Use Quorum Hibernate
 sidebar_position: 4
-description: Use Quorum Hibernate with Hyperledger Besu
+description: Use Quorum Hibernate with Besu
 tags:
   - private networks
 ---

diff --git a/docs/private-networks/how-to/monitor/splunk.md b/docs/private-networks/how-to/monitor/splunk.md
@@ -2,7 +2,7 @@
 title: Use Splunk
 sidebar_position: 5
 toc_max_heading_level: 2
-description: Send Hyperledger Besu logs to Splunk
+description: Send Besu logs to Splunk
 tags:
   - private networks
 ---

diff --git a/docs/private-networks/how-to/send-transactions/concurrent-private-transactions.md b/docs/private-networks/how-to/send-transactions/concurrent-private-transactions.md
@@ -1,6 +1,6 @@
 ---
 title: Send concurrent private transactions
-description: Creating and sending concurrent private transactions with Hyperledger Besu
+description: Creating and sending concurrent private transactions with Besu
 sidebar_position: 2
 tags:
   - private networks

diff --git a/docs/private-networks/how-to/send-transactions/private-transactions.md b/docs/private-networks/how-to/send-transactions/private-transactions.md
@@ -1,6 +1,6 @@
 ---
 title: Create and send private transactions
-description: Creating and sending private transactions with Hyperledger Besu
+description: Creating and sending private transactions with Besu
 sidebar_position: 1
 tags:
   - private networks

diff --git a/docs/private-networks/how-to/send-transactions/revert-reason.md b/docs/private-networks/how-to/send-transactions/revert-reason.md
@@ -1,6 +1,6 @@
 ---
 title: Include revert reason
-description: Including revert reason in transactions with Hyperledger Besu
+description: Including revert reason in transactions with Besu
 sidebar_position: 3
 tags:
   - private networks
@@ -40,7 +40,7 @@ contract VendingMachine {
 
 ## Enable revert reason
 
-Use the [`--revert-reason-enabled`](../../../public-networks/reference/cli/options.md#revert-reason-enabled) command line option to include the revert reason in the transaction receipt and the [`trace`](../../../public-networks/reference/trace-types.md#trace) response in Hyperledger Besu.
+Use the [`--revert-reason-enabled`](../../../public-networks/reference/cli/options.md#revert-reason-enabled) command line option to include the revert reason in the transaction receipt and the [`trace`](../../../public-networks/reference/trace-types.md#trace) response in Besu.
 
 :::caution
 

diff --git a/docs/private-networks/how-to/use-permissioning/local.md b/docs/private-networks/how-to/use-permissioning/local.md
@@ -1,7 +1,7 @@
 ---
 title: Use local permissioning
 sidebar_position: 1
-description: Hyperledger Besu local permissioning
+description: Besu local permissioning
 tags:
   - private networks
 ---
@@ -32,7 +32,7 @@ Local permissioning doesn't check that the node using the permissions configurat
 
 ### Specify bootnodes in the allowlist
 
-The nodes permissions list must include the [bootnodes](../configure/bootnodes.md) or Hyperledger Besu doesn't start with node permissions enabled.
+The nodes permissions list must include the [bootnodes](../configure/bootnodes.md) or Besu doesn't start with node permissions enabled.
 
 If you start Besu with specified bootnodes and have node permissioning enabled:
 

diff --git a/docs/private-networks/how-to/use-privacy/access-private-transactions.md b/docs/private-networks/how-to/use-privacy/access-private-transactions.md
@@ -1,14 +1,14 @@
 ---
 title: Access private and privacy marker transactions
-description: Methods for accessing and managing private transactions and privacy groups in Hyperledger Besu
+description: Methods for accessing and managing private transactions and privacy groups in Besu
 sidebar_position: 6
 tags:
   - private networks
 ---
 
 # Access private and privacy marker transactions
 
-A Hyperledger Besu private transaction creates a [privacy marker transaction](../../concepts/privacy/private-transactions/processing.md) and the private transaction itself.
+A Besu private transaction creates a [privacy marker transaction](../../concepts/privacy/private-transactions/processing.md) and the private transaction itself.
 
 ## Transaction receipts
 

diff --git a/docs/private-networks/how-to/use-privacy/besu-extended.md b/docs/private-networks/how-to/use-privacy/besu-extended.md
@@ -1,14 +1,14 @@
 ---
 title: Use Besu-extended privacy
-description: Hyperledger Besu-extended privacy
+description: Besu-extended privacy
 sidebar_position: 2
 tags:
   - private networks
 ---
 
 # Use Besu-extended privacy
 
-Hyperledger Besu provides an extended implementation of privacy allowing you to [create a privacy group for a set of participants](../../concepts/privacy/privacy-groups.md). You must specify the privacy group ID when sending private transactions.
+Besu provides an extended implementation of privacy allowing you to [create a privacy group for a set of participants](../../concepts/privacy/privacy-groups.md). You must specify the privacy group ID when sending private transactions.
 
 To enable the [`PRIV` API methods](../../reference/api/index.md#priv-methods), use the [`--rpc-http-api`](../../../public-networks/reference/cli/options.md#rpc-http-api) or [`--rpc-ws-api`](../../../public-networks/reference/cli/options.md#rpc-ws-api) command line options.
 

diff --git a/docs/private-networks/how-to/use-privacy/eea-compliant.md b/docs/private-networks/how-to/use-privacy/eea-compliant.md
@@ -1,14 +1,14 @@
 ---
 title: Use EEA-compliant privacy
-description: Hyperledger Besu JSON-RPC methods to use for EEA-compliant privacy
+description: Besu JSON-RPC methods to use for EEA-compliant privacy
 sidebar_position: 1
 tags:
   - private networks
 ---
 
 # Use EEA-compliant privacy
 
-When using Hyperledger Besu [EEA-compliant privacy](../../concepts/privacy/privacy-groups.md), the group of nodes specified by `privateFrom` and `privateFor` form a privacy group, to which Tessera assigns a unique privacy group ID.
+When using Besu [EEA-compliant privacy](../../concepts/privacy/privacy-groups.md), the group of nodes specified by `privateFrom` and `privateFor` form a privacy group, to which Tessera assigns a unique privacy group ID.
 
 To enable the [`EEA` API methods](../../reference/api/index.md#eea-methods), use the [`--rpc-http-api`](../../../public-networks/reference/cli/options.md#rpc-http-api) or [`--rpc-ws-api`](../../../public-networks/reference/cli/options.md#rpc-ws-api) command line options.
 

diff --git a/docs/private-networks/how-to/use-privacy/privacy-groups.md b/docs/private-networks/how-to/use-privacy/privacy-groups.md
@@ -1,14 +1,14 @@
 ---
 title: Create and manage privacy groups
-description: Create and manage privacy groups with Hyperledger Besu
+description: Create and manage privacy groups with Besu
 sidebar_position: 4
 tags:
   - private networks
 ---
 
 # Create and manage privacy groups
 
-Hyperledger Besu-extended privacy provides JSON-RPC API methods for creating and managing privacy groups:
+Besu-extended privacy provides JSON-RPC API methods for creating and managing privacy groups:
 
 - [`priv_createPrivacyGroup`](../../reference/api/index.md#priv_createprivacygroup)
 - [`priv_findPrivacyGroup`](../../reference/api/index.md#priv_findprivacygroup)

diff --git a/docs/private-networks/how-to/use-privacy/sign-pmts.md b/docs/private-networks/how-to/use-privacy/sign-pmts.md
@@ -1,14 +1,14 @@
 ---
 title: Sign privacy marker transactions
-description: How to sign a privacy marker transaction with Hyperledger Besu
+description: How to sign a privacy marker transaction with Besu
 sidebar_position: 7
 tags:
   - private networks
 ---
 
 # Sign privacy marker transactions
 
-You can sign privacy marker transactions (PMTs) with either a random key or a specified key. To sign privacy marker transactions with a specified private key, use [`--privacy-marker-transaction-signing-key-file`](../../reference/cli/options.md#privacy-marker-transaction-signing-key-file) when starting Hyperledger Besu.
+You can sign privacy marker transactions (PMTs) with either a random key or a specified key. To sign privacy marker transactions with a specified private key, use [`--privacy-marker-transaction-signing-key-file`](../../reference/cli/options.md#privacy-marker-transaction-signing-key-file) when starting Besu.
 
 :::note
 

diff --git a/docs/private-networks/how-to/use-privacy/tessera.md b/docs/private-networks/how-to/use-privacy/tessera.md
@@ -1,14 +1,14 @@
 ---
 title: Run Tessera with Besu
-description: Running ConsenSys Quorum Tessera with Hyperledger Besu
+description: Running ConsenSys Quorum Tessera with Besu
 sidebar_position: 3
 tags:
   - private networks
 ---
 
 # Run Tessera with Besu
 
-To enable [privacy functionality](../../concepts/privacy/index.md) in production systems, [Tessera](https://docs.tessera.consensys.net/) must be [highly available](#high-availability) and [run in a separate instance](#separate-instances) to Hyperledger Besu.
+To enable [privacy functionality](../../concepts/privacy/index.md) in production systems, [Tessera](https://docs.tessera.consensys.net/) must be [highly available](#high-availability) and [run in a separate instance](#separate-instances) to Besu.
 
 ![Besu-Tessera-High-Availability](../../../assets/images/Besu-Tessera-High-Availability.png)
 

diff --git a/docs/private-networks/how-to/use-privacy/web3js-quorum.md b/docs/private-networks/how-to/use-privacy/web3js-quorum.md
@@ -41,7 +41,7 @@ npm install web3js-quorum
 ## Initialize the web3js-quorum client
 
 Initialize your client where `<JSON-RPC HTTP endpoint>` is the JSON-RPC HTTP endpoint of your
-Hyperledger Besu node.
+Besu node.
 Specified by the [`--rpc-http-host`](../../../public-networks/reference/cli/options.md#rpc-http-host)
 and [`--rpc-http-port`](../../../public-networks/reference/cli/options.md#rpc-http-port) command
 line options.