manual, update new pr

collections/farmers/3node_building/minting_receipts.md

@@ -5,6 +5,7 @@
 - [Introduction](#introduction)
 - [Access the Reports](#access-the-reports)
 - [Available Information](#available-information)
+- [TFT Farming Registration Price](#tft-farming-registration-price)
 
 ***
 
@@ -22,11 +23,11 @@ Once you have the receipt hash of your node minting, you can get the [minting re
 
 The ThreeFold Alpha minting tool will present the following information for each minting receipt hash:
 
-- Node Info
+- Node Info: This contains the basic information in relation to your node.
   - Node ID
   - Farm Name and ID
   - Measured Uptime
-- Node Resources
+- Node Resources: These resources are related to the [cloud units](cloud@@cloudunits) and the [resource units](cloud@@resource_units_calc_cloudunits).
   - CU
   - SU
   - NU
@@ -34,5 +35,11 @@ The ThreeFold Alpha minting tool will present the following information for each
   - MRU
   - SRU
   - HRU
-- TFT Farmed
-- Payout Address
+- TFT Farmed: This is the quantity of TFT farmed during the minting period.
+- Payout Address: The payout address is the Stellar address you set to receive your farming rewards.
+
+## TFT Farming Registration Price
+
+Currently, minting is set at a TFT value of 0.08 USD. This TFT farming registration price (i.e. the TFT minting value) can be seen as a farming difficulty level. The higher this number is, the less TFT is minted for the same given node. This number is not related to the TFT market price and is currently fixed. 
+
+The ThreeFold DAO can vote to change this number. For example, if the ThreeFold DAO decides to increase the TFT minting value to 0.10 USD, the farming difficulty would be increased by 25% (0.08 * 1.25 = 0.10). This updated TFT farming registration price would then affect all new nodes that are registered after the DAO vote is passed.

collections/farmers/advanced_networking/network_setup.md

@@ -28,7 +28,7 @@ The nodes themselves can have connectivity in a few different ways:
 
 - Only have RFC1918 private addresses, connected to the Internet through NAT, NO IPv6
   Mostly, these are single-NIC (Network card) machines that can host some workloads through the Overlay Network, but 
-  cant't expose services directly. These are HIDDEN nodes, and are mostly booted with an USB stick from 
+  can't expose services directly. These are HIDDEN nodes, and are mostly booted with an USB stick from 
   bootstrap.grid.tf .
 - Dual-stacked: having RFC1918 private IPv4 and public IPv6 , where the IPv6 addresses are received from a home router, 
 but firewalled for outgoing traffic only. These nodes are effectively also HIDDEN
@@ -70,9 +70,9 @@ Use your (home) ISP router Ipv6 DHCP capabilities to provide (private) IPv6 addr
 
 ### 2.2 Data Center/Advanced Setup
 
-In this situation there are many options on how to setup you node.  This requires you as the expert to make a few decisions on how to connect what what the best setup is that you can support for the operaitonal time of your farm.  The same basics principles apply:
-  - You have to have a block of (public) IPv6 routed to you router, or you have to have your router setup to provide Network Address Translation (NAT)
-  - You have to have a DHCP server in your network that manages and controls IPV6 ip adress leases.  Depending on your specific setup you have this DHCP server manage a public IPv6y range which makes all nodes directly connected to the public internet or you have this DHCP server manage a private block og IPv6 addresses which makes all you nodes connect to the internet through NAT.  
+In this situation there are many options on how to setup your node.  This requires you as the expert to make a few decisions on how to connect what what the best setup is that you can support for the operaitonal time of your farm.  The same basics principles apply:
+  - You have to have a block of (public) IPv6 routed to your router, or you have to have your router setup to provide Network Address Translation (NAT)
+  - You have to have a DHCP server in your network that manages and controls IPV6 ip adress leases.  Depending on your specific setup you have this DHCP server manage a public IPv6 range which makes all nodes directly connected to the public internet or you have this DHCP server manage a private block of IPv6 addresses which makes all your nodes connect to the internet through NAT.  
 
 As a farmer you are in charge of selecting and creating the appropriate network setup for your farm.  
 

collections/farmers/farmerbot/farmerbot_information.md

@@ -36,6 +36,8 @@
   - [Properly reboot the node if power target "Down" doesn't work](#properly-reboot-the-node-if-power-target-down-doesnt-work)
   - [Add a 3Node to a running Farmerbot](#add-a-3node-to-a-running-farmerbot)
   - [Update the Farmerbot with a new release](#update-the-farmerbot-with-a-new-release)
+- [Troubleshooting](#troubleshooting)
+  - [Can't Find the Logs](#cant-find-the-logs)
 - [Questions and Feedback](#questions-and-feedback)
 
 ***
@@ -431,6 +433,18 @@ There are only a few steps needed to update the Farmerbot to a new release.
   rm tfgrid-sdk-go_Linux_x86_64.tar.gz
   ```
 
+# Troubleshooting
+
+## Can't Find the Logs
+
+If you can't find the logs of the Farmerbot, make sure that you ran the bot before! Once the Farmerbot runs, it should print logs in a file called `farmerbot.log` in the directory where it is running.
+
+You can try a search for any files under the home directory with the `.log` extension in case it's been moved:
+
+```
+find ~/ -name '*.log'
+```
+
 # Questions and Feedback
 
 If you have questions concerning the Farmerbot, feel free to ask for help on the [ThreeFold Forum](https://forum.threefold.io/) or on the [ThreeFold Farmer chat](https://t.me/threefoldfarmers).