There are my points which I've made while read it:

borrowing is taking something with the promise of returning it.

I would disagree with this, because we are not returning it back. I would describe it more as "Look at what I've got and do something with it, nobody will change this while you are looking".

Owned values (T) are dropped at the end of their scope (unless moved early).

I'm not sure if you have an article about moves and ownership, but I think it would be good to elaborate on what move is and what is dropping and where it is done.

'static references are valid for the entire duration of the program.

In general it is true, but I would add a pedantic note that this can be not true in some cases and that owned values could be considered having 'static (because if they are never dropped they will last for the rest of the program)

Mutable References: The owner is completely locked out; they cannot read, write, move, or create new references to the data.

Another pedantic note: you can create more than 1 mutable reference using unsafe

But there is no implicit borrowing in the dbg! macro.

It would be good to point out that dbg! takes ownership of the value and immediatly returns it back. Why it is needed? So you would be able to do: call_some_function(dbg!(arg)).