Merge branch 'main' into new_docs_update

Author: robertagora

.github/workflows/update-versions.yml

@@ -0,0 +1,50 @@
+name: Update Lotus Version
+
+on:
+  workflow_dispatch:  # Allows manual trigger
+  pull_request:
+    types: [opened, reopened]
+
+jobs:
+  update-version:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '18'
+      
+      - name: Get latest Lotus version
+        id: get-version
+        run: |
+          # Get all releases and find the first one starting with 'v'
+          RELEASE_INFO=$(curl -s "https://api.github.com/repos/filecoin-project/lotus/releases" | \
+            jq -r '[.[] | select(.tag_name | startswith("v"))] | first')
+          
+          # Extract the tag name
+          TAG_NAME=$(echo "$RELEASE_INFO" | jq -r .tag_name)
+          
+          # Extract version number (remove 'v' prefix)
+          LATEST_VERSION=$(echo $TAG_NAME | sed 's/^v//')
+          
+          echo "LATEST_VERSION=$LATEST_VERSION" >> $GITHUB_ENV
+          echo "TAG_NAME=$TAG_NAME" >> $GITHUB_ENV
+
+      - name: Run update script
+        run: |
+          node update-versions.js ${{ env.LATEST_VERSION }}
+          
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v5
+        with:
+          commit-message: 'Chore: update Lotus version references to ${{ env.LATEST_VERSION }}'
+          title: 'Chore: update Lotus version references to ${{ env.LATEST_VERSION }}'
+          body: |
+            Automated PR to update Lotus version references to ${{ env.LATEST_VERSION }}
+            
+            This PR was automatically generated by GitHub Actions.
+          branch: update-lotus-version
+          base: main
+          delete-branch: true

builder-cookbook/dapps/chain-data-query.md

@@ -30,8 +30,8 @@ We will use `ethers.js` to establish a connection with the public Filecoin node
 import { ethers } from "ethers"
 
 //The public Filecoin calibration URL
-const fielcoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
-const provider = new ethers.JsonRpcProvider(fielcoin_url)
+const filecoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
+const provider = new ethers.JsonRpcProvider(filecoin_url)
 
 const blockNumber = await provider.getBlockNumber()
 console.log("Block height: ", blockNumber)
@@ -69,8 +69,8 @@ import { ethers } from "ethers"
 const wFILAddress = "0xaC26a4Ab9cF2A8c5DBaB6fb4351ec0F4b07356c4" // wFIL Contract
 var abi = ["event Transfer(address indexed from, address indexed to, uint amount)"]
 
-const fielcoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
-const provider = new ethers.providers.JsonRpcProvider(fielcoin_url)
+const filecoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
+const provider = new ethers.providers.JsonRpcProvider(filecoin_url)
 
 //listen to the Transfer events in the Token contract
 const wFIL = new ethers.Contract(wFILAddress, abi, provider)
@@ -110,8 +110,8 @@ import { ethers } from "ethers"
 const wFILAddress = "0xaC26a4Ab9cF2A8c5DBaB6fb4351ec0F4b07356c4" // wFIL Contract
 var abi = ["event Transfer(address indexed from, address indexed to, uint amount)"]
 
-const fielcoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
-const provider = new ethers.providers.JsonRpcProvider(fielcoin_url)
+const filecoin_url = 'https://api.calibration.node.glif.io/rpc/v1'
+const provider = new ethers.providers.JsonRpcProvider(filecoin_url)
 
 // Create a filter to list all token transfers from myAddress
 const filter = contract.filters.Transfer("0xd388aB098ed3E84c0D808776440B48F685198498");

builder-cookbook/dapps/decentralized-database.md

@@ -44,7 +44,7 @@ To track all the deal aggregation/RaaS requests submitted to the smart contract,
 
 ```solidity
 uint256 private tableId;
-string private constant _TABLE_PREFIX = "aggregaor_table"; // Custom table prefix
+string private constant _TABLE_PREFIX = "aggregator_table"; // Custom table prefix
 
 // Constructor that creates a table, sets the controller, and inserts data
 constructor() {

nodes/full-nodes/basic-setup.md

@@ -12,31 +12,29 @@ To install Lotus on your computer, follow these steps:
 2. Once you have downloaded the binary file, extract the contents to a directory of your choice. For example, if you are using Linux, you can extract the contents to the `/usr/local/bin directory` by running the command:
 
 ```sh
-sudo tar -C /usr/local/bin -xzf lotus-X.X.X-linux-amd64.tar.gz
+sudo tar -C /usr/local/bin -xzf lotus-1.31.1-linux-amd64.tar.gz
 ```
 
-3. Replace `X.X.X` with the version number of the release you downloaded.
-4. After extracting the contents, navigate to the `lotus` directory in your terminal. For example, if you extracted the contents to `/usr/local/bin`, you can navigate to the lotus directory by running the command:
+3. After extracting the contents, navigate to the `lotus` directory in your terminal. For example, if you extracted the contents to `/usr/local/bin`, you can navigate to the lotus directory by running the command:
 
 ```sh
-cd /usr/local/bin/lotus-X.X.X
+cd /usr/local/bin/lotus-1.31.1
 ```
 
-5. Again, replace `X.X.X` with the version number of the release you downloaded.
-6. Run the `lotus` binary file to start the Lotus daemon. You can do this by running the command:
+4. Run the `lotus` binary file to start the Lotus daemon. You can do this by running the command:
 
 ```sh
 ./lotus daemon
 ```
 
-7. This will start the Lotus daemon, which will connect to the Filecoin network and start synchronizing with other nodes on the network.
-8. Optionally, you can also run the lotus-miner binary file if you want to participate in the Filecoin mining process. You can do this by running the command:
+5. This will start the Lotus daemon, which will connect to the Filecoin network and start synchronizing with other nodes on the network.
+6. Optionally, you can also run the lotus-miner binary file if you want to participate in the Filecoin mining process. You can do this by running the command:
 
 ```sh
 ./lotus-miner run
 ```
 
-9. This will start the Lotus miner, which will use your computer’s computing power to mine new blocks on the Filecoin network.
+7. This will start the Lotus miner, which will use your computer’s computing power to mine new blocks on the Filecoin network.
 
 
 

nodes/lite-nodes/spin-up-a-lite-node.md

@@ -73,12 +73,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
     This should output something like:
 
     ```output
-    v1.29.0
+    v1.31.1
     ```
 3.  Using the value returned from the previous command, checkout to the latest release branch:
 
     ```shell
-    git checkout v1.29.0
+    git checkout v1.31.1
     ```
 4. Done! You can move on to the [Build](https://docs.filecoin.io/nodes/lite-nodes/spin-up-a-lite-node/#build-the-binary) section.
 {% endtab %}
@@ -99,12 +99,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
     This should output something like:
 
     ```output
-    v1.29.0
+    v1.31.1
     ```
 3.  Using the value returned from the previous command, checkout to the latest release branch:
 
     ```shell
-    git checkout v1.29.0
+    git checkout v1.31.1
     ```
 4.  Create the necessary environment variables to allow Lotus to run on M1 architecture:
 
@@ -132,12 +132,12 @@ Before we can build the Lotus binaries, we need to follow a few pre-build steps.
     This should output something like:
 
     ```output
-    v1.29.0
+    v1.31.1
     ```
 3.  Using the value returned from the previous command, checkout to the latest release branch:
 
     ```shell
-    git checkout v1.29.0
+    git checkout v1.31.1
     ```
 4.  If your processor was released later than an AMD Zen or Intel Ice Lake CPU, enable SHA extensions by adding these two environment variables. If in doubt, ignore this command and move on to [the next section](https://docs.filecoin.io/nodes/lite-nodes/spin-up-a-lite-node/#build-the-binary).
 
@@ -175,7 +175,7 @@ The last thing we need to do to get our node setup is to build the package. The
     This will output something like:
 
     ```plaintext
-    lotus version 1.29.0+mainnet+git.1ff3b360b
+    lotus version 1.31.1+mainnet+git.1ff3b360b
     ```
 {% endtab %}
 
@@ -200,7 +200,7 @@ The last thing we need to do to get our node setup is to build the package. The
     This will output something like:
 
     ```plaintext
-    lotus version 1.29.0+calibnet+git.1ff3b360b
+    lotus version 1.31.1+calibnet+git.1ff3b360b
     ```
 {% endtab %}
 {% endtabs %}

package.json

@@ -0,0 +1,21 @@
+{
+  "name": "filecoin-docs",
+  "version": "1.0.0",
+  "description": "<div align=center>",
+  "main": "update-versions.js",
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1",
+    "update-versions": "node update-versions.js"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/filecoin-project/filecoin-docs.git"
+  },
+  "keywords": [],
+  "author": "",
+  "license": "ISC",
+  "bugs": {
+    "url": "https://github.com/filecoin-project/filecoin-docs/issues"
+  },
+  "homepage": "https://github.com/filecoin-project/filecoin-docs#readme"
+}

reference/built-in-actors/protocol-api.md

@@ -1181,7 +1181,7 @@ Results:
 
 ## Verified registry actor
 
-Verified registry actor is responsible for managing verified clients. The ActorCode for the verified registry built-in actor is `hex"0006"` which will be used to call the exported methods in the verified registry built-in actor. You need to specify the method number for the method you want to invoke. Please referer to each method for its method number.
+Verified registry actor is responsible for managing verified clients. The ActorCode for the verified registry built-in actor is `hex"0006"` which will be used to call the exported methods in the verified registry built-in actor. You need to specify the method number for the method you want to invoke. Please refer to each method for its method number.
 
 ### AddVerifiedClient
 
@@ -1273,7 +1273,7 @@ Params:
 * `struct` ExtendClaimTermsParams
   * `struct ClaimTerm[]` Terms
     * `uint64` Provider - The provider address which stores the data.
-    * `uint64` CliamID - Claim ID.
+    * `uint64` ClaimID - Claim ID.
     * `int64` TermMax - The max chain epoch to extend.
 
 Results:

reference/general/README.md

@@ -75,7 +75,7 @@ Developer tools, API clients & storage services that developers can use to build
 
 ### Storage APIs for app builders
 
-* [Lighthouse](https://www.lighthouse.storage/) - Lighthouse offers a suite of tools to enable builders to store data on Filecoin when biulding apps.
+* [Lighthouse](https://www.lighthouse.storage/) - Lighthouse offers a suite of tools to enable builders to store data on Filecoin when building apps.
 * [`NFT.storage`](https://nft.storage/) - Preserve your NFTs with our new low-cost, easy-to-use solution, ensuring verifiable long-term storage on Filecoin.
 * [`Web3.storage`](https://web3.storage/) - service from Protocol Labs for storing off-chain _dApp_ data on IPFS and Filecoin, with help from Pinata (a fast IPFS Pinning Service) to [distribute the content across IPFS](https://www.pinata.cloud/blog/protocol-labs-and-pinata)
 * [`Textile.io's tools`](https://docs.textile.io/) - suite of tools for interacting with IPFS and Filecoin, including [Tableland](https://tableland.xyz/) and Filecoin bridges to Polygon and NEAR.

reference/json-rpc/client.md

@@ -1,7 +1,7 @@
 # Client
 
 {% hint style="warning" %}
-The Client methods are now deprecated and have been removed from Lotus (the Filecoin reference implemenation).
+The Client methods are now deprecated and have been removed from Lotus (the Filecoin reference implementation).
 {% endhint %}
 
 Some similar functionality can be found by using the [Boostly](https://github.com/filecoin-shipyard/boostly) library, which interacts with market actors provided by [Boost](https://boost.filecoin.io/).

reference/json-rpc/create.md

@@ -2,7 +2,7 @@
 
 ## CreateBackup
 
-CreateBackup creates node backup onder the specified file name. The method requires that the lotus daemon is running with the LOTUS\_BACKUP\_BASE\_PATH environment variable set to some path, and that the path specified when calling CreateBackup is within the base path
+CreateBackup creates node backup under the specified file name. The method requires that the lotus daemon is running with the LOTUS\_BACKUP\_BASE\_PATH environment variable set to some path, and that the path specified when calling CreateBackup is within the base path
 
 Perms: admin