Do not reference machine 'pointers' in explanation of 'size' types.

Simplify explanation and rephrase as per @GuillaumeGomez's suggestion.

Replace "make for" by the slightly more accurate "account for".

Reading this, one item stood out a bit. Small improvements here.

. ‘Compile-time’ is not a noun, ‘compilation time’ was meant;
. Mathematical formulas are best not rendered as code;
. Use the same tense as in other items.

Clarification by more precise specification.

The code examples and previous paragraphs all use `v` and `v2`

…labnik

Avoid linking to itself in implementors section of trait page

Fix rust-lang#32474.

…labnik

Reword explanation of 'size' types.

Do not reference machine 'pointers' in explanation of 'size' types.

I think the number of elements that can be directly addressed is a fundamental feature of a machine architecture in its own right. The fact that it coincides with the ‘size’ of a pointer should be viewed as an ‘implementation detail’ ;)

Do not use "bind" to refer to both referencing and to assignment

See https://users.rust-lang.org/t/difference-between-four-references/5406/7

grammar: fix

Reading this, one item stood out a bit. Small improvements here.

1. ‘Compile-time’ is not a noun, ‘compilation time’ was meant;
1. Mathematical formulas are best not rendered as code;
1. Use the same tense as in other items.