Actual: "The wallet will first download and validate the latest :ref:’macroblock’ and then all the rest of the blockchain."
Expected: "The wallet will first download and validate the latest macroblock and then all the rest of the blockchain."

Actual: "Before starting to receive BEAM for the first time, please read first about what :ref:’address’ is."
Expected: "Before starting to receive BEAM for the first time, please read first about what address is."

Actual: "‘Send’ and ‘Receive’ buttons at the top right corner help us to Sending BEAM and Receiving BEAM."
Expected: "‘Send’ and ‘Receive’ buttons at the top right corner help us to Sending BEAM and Receiving BEAM."

Actual: "Proceed to install Beam Wallet Mobile App by going to the Google Play store."
Expected: "Proceed to install Beam Wallet Mobile App by going to the Google Play store."

Actual: "The comment can be seen on the :ref:’Address screen’ and in the extended transaction view."
Expected: "
The comment can be seen on the Address screen and in the extended transaction view."

Remove the link in the brackets and add it to the "Beam Community" text

Actual:" ... and joining Beam Community on Telegram (https://t.me/BeamPrivacy) for updates and discussions."

Expected: " ... and joining Beam Community on Telegram for updates and discussions."

After typing the password as I press enter, beam wallet disappears on windows 10.
Even the task manager does not have it.
But if I do not enter pass? it seems fine.

Please advise what to do.
Kind Regards
Abdul Wahab

Due to new release Bright Boson 2.0.4739 docs need to be updated.

Information - https://github.com/BeamMW/beam/releases

Actual: "‘Send’ and ‘Receive’ buttons at the top right corner help us to Sending BEAM and Receiving BEAM."
Expected: "‘Send’ and ‘Receive’ buttons at the top right corner help us to Sending BEAM and Receiving BEAM."

Change the link from http://beam.mw/ to https://beam.mw/

Actual: "The concept of Address is completely different"
Expected: "The concept of Address is completely different"

Actual: "The comment can be seen on the :ref:’Address screen’:"
Expected: "The comment can be seen on the Address screen:"

Actual: "Once Beam Wallet desktop app is installed, the wallet data filers are stored separately from the binaries."
Expected: "Once Beam Wallet desktop app is installed, the wallet data files are stored separately from the binaries."

Update the table of contents for Beam 6.0 release

Actual: "Before starting to send BEAM, please read first about what :ref:’Address’ is."
Expected: "Before starting to send BEAM, please read first about what Address is."

Actual: "The comment can be seen on the :ref:’Address screen’:"
Expected: "The comment can be seen on the Address screen"

The "key_owner" and "key_mine" parameters are deprecated, use "owner_key" and "miner_key" accordingly.

Actual: "..note::When the Beam wallet app is running, right click on it and select Options | Keep in dock for easy access of the app in the future."

Actual: "For integrated and external nodes settings see Choosing the node connectivity mode."
Expected: "For integrated and external nodes settings see Choosing the node connectivity mode."

In several places in the docs it is mentioned that the .cfg file is looked for in the "same folder as Beam Node binary" for example.

This is incorrect. The .cfg is searched for in your current working directory and not in the location of the executable. At least on linux.

I.e., If I am in my home directory and I run BeamWallet or beam-node (and the executable is in /usr/bin for example) it looks for the .cfg in the home directory. If I switch to any other directory and run from there... the .cfg is expected to be in the new current working directory. If you run BeamWallet from the desktop menus --assuming you have it correctly configured for that (for example, from the GNOME launcher)-- the default working directory generally becomes the user's home directory (though sometimes the process for other applications will kick the pwd to root /).

Anyway. The docs are a bit misleading on this point. Thanks! -t
(t0dd on discord and lots of other places)

Hi, I want to develop a GUI application which controls the miner software but I want to integrate this within The Rust programming language therefore I end up generating one executable in it.

Is this even possible?

Actual: "The comment can be seen on the :ref:’Address screen’ and in the extended transaction view."
Expected: "The comment can be seen on the Address screen and in the extended transaction view."

Actual: "The wallet will first download and validate the latest :ref:’macroblock’ and then all the rest of the blockchain."
Expected: "The wallet will first download and validate the latest macroblock and then all the rest of the blockchain."

Actual: "A person can create as many addresses as required. The address creation process is explained in Receiving BEAM."
Expected: "A person can create as many addresses as required. The address creation process is explained in Receiving BEAM."

Actual: "Addresses are merely merely private / public key pairs used to encrypt and decrypt these messages."
Expected; "Addresses are merely private / public key pairs used to encrypt and decrypt these messages."

Actual: "‘Send’ and ‘Receive’ buttons at the top right corner help us to Sending BEAM and Receiving BEAM."
Expected: "‘Send’ and ‘Receive’ buttons at the top right corner help us with Sending BEAM and Receiving BEAM."

Actual: "Before starting to receive BEAM for the first time, please read first about what :ref:’address’ is."
Expected: "Before starting to receive BEAM for the first time, please read first about what address is."

Actual: Logs (see :ref: log locations for information where to find the logs files)
Expected: Logs (see log locations for information where to find the logs files)