Merge pull request #195 from sei-protocol/alexander-sei-patch-1

Smaller cleanup

pages/dev-node/node-operators.mdx

@@ -16,6 +16,24 @@ import VersionTable from '../../components/VersionFetcher/VersionTable';
 
 _The following instructions are for Debian-based systems. Other operating systems like macOS or Arch will use a slightly different procedure._
 
+## Option 1: Install from Precompiled Binaries
+If you prefer not to build seid from source, you can use precompiled binaries. Make sure to select the correct architecture for your machine (e.g., linux-amd64 for typical 64-bit Linux systems, darwin-arm64 for macOS).
+
+Head to [sei-binares](https://github.com/alexander-sei/sei-binaries/releases) to pick the release. Download and install it as follows:
+
+```
+cd ~
+
+# Replace <The_link_of_the_binary> with the link the precompiled binary
+wget -O seid <The_link_of_the_binary>
+
+# Copy the binary into your PATH (e.g., /usr/local/bin)
+sudo cp seid /usr/local/bin/seid
+sudo chmod +x /usr/local/bin/seid
+```
+
+## Option 2: Manually compiling seid 
+
 ### Update and Upgrade System Packages
 
 ```bash
@@ -74,6 +92,8 @@ git checkout $VERSION
 make install
 ```
 
+## Initialize and Configure the Node
+
 ### Initialize Node
 
 1. Initialize the node:

pages/dev-querying-state.mdx

@@ -38,8 +38,6 @@ Archive nodes, on the other hand, store the entire history of the blockchain fro
 
 •	**Use Cases**: Archive nodes are crucial for tasks that require access to historical data, such as catching up indexers, conducting historical analysis, and verifying past transactions.
 
-## **Querying by Block Height**
-
 ## **Using Indexers for Historical Data**
 
 While archive nodes provide the raw historical data, indexers are essential for efficiently querying and analyzing this data. Indexers organize and optimize the data, making it easier to access and analyze.