Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/vocs/docs/pages/guides/history-expiry.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: Usage of tools for importing, exporting and pruning historical bloc

In this chapter, we will learn how to use tools for dealing with historical data, it's import, export and removal.

We will use [reth cli](../cli/cli) to import and export historical data.
We will use [reth cli](/cli/cli) to import and export historical data.

## Enabling Pre-merge history expiry

Expand Down Expand Up @@ -49,7 +49,7 @@ When enabled, the import from ERA1 files runs as its own separate stage before a

### Manual import

If you want to import block headers and transactions from ERA1 files without running the synchronization pipeline, you may use the [`import-era`](../cli/reth/import-era) command.
If you want to import block headers and transactions from ERA1 files without running the synchronization pipeline, you may use the [`import-era`](/cli/reth/import-era) command.

### Options

Expand All @@ -68,7 +68,7 @@ Both options cannot be used at the same time. If no option is specified, the rem
In this section we discuss how to export blocks data into ERA1 files.

### Manual export
You can manually export block data from your database to ERA1 files using the [`export-era`](../cli/reth/export-era) command.
You can manually export block data from your database to ERA1 files using the [`export-era`](/cli/reth/export-era) command.

The CLI reads block headers, bodies, and receipts from your local database and packages them into the standardized ERA1 format with up to 8,192 blocks per file.

Expand Down