raw_reserve behavior is incorrectly described in docs

[Skydev0h]

Describe the bug

raw_reserve is described as equivalent to sending the message to "the sender", that is incorrect and confuses developers, because it actually is equivalent to sending the message to oneself, that is, the current smart contract (in simpler terms)

To reproduce

1. Go to https://docs.ton.org/v3/documentation/smart-contracts/func/docs/stdlib#raw_reserve
2. Observe incorrect description (to the sender)

Expected behavior

It should be described as sending to "oneself", or the current smart contract in simpler to understand terms.

See the original TVM spec: https://docs.ton.org/tvm.pdf

Screenshots

Desktop (please complete the following information)

No response

Smartphone (please complete the following information)

No response

Additional context

No response

[memearchivarius]

@Skydev0h Thank you for the contribution!
I suppose sender is the contract you are working with, in the message you have two fields:

• source (sender)
• destination (receiver)

So in these terms you are creating "a message that transfers the amount to the sender" (this contract).
But you are correct that it might be confusing, we'll review the wording.

[Skydev0h]

@Skydev0h Thank you for the contribution! I suppose sender is the contract you are working with, in the message you have two fields:

• source (sender)
• destination (receiver)

So in these terms you are creating "a message that transfers the amount to the sender" (this contract). But you are correct that it might be confusing, we'll review the wording.

Maybe maybe, "oneself" in original spec is also quite confusing. However, when processing a message, a developer will most likely think that "sender" is sender of a message that is being processed, and I actually stumbled upon this situation today, when other developer thought that raw_reserve sends funds back to message sender because of the documentation.

Thus, even such rewording will make it less confusing.

Thanks!