docs improvements

Author: robamu

link.x.in

@@ -92,6 +92,7 @@ Possible solutions, from most likely to less likely:
   pac crate
 - Disable the 'device' feature of msp430-rt to build a generic application; a dependency
 may be enabling it
+- Override __VECTORS_END_ADDR if your vector table is not placed at the regular vector location
 ");
 
 ASSERT(_sgot == _egot, "

src/lib.rs

@@ -63,6 +63,12 @@
 //! }
 //! ```
 //!
+//! By default, the linker will check that the address after the vector table is 0x10000 to
+//! ensure that the vector table is placed correctly. For special cases like bootloader
+//! setups, you might want to place the vector table somewhere else. For theses cases,
+//! you can re-configure the expected end address by setting `__VECTORS_END_ADDR` in your
+//! `memory.x` file.
+//!
 //! # An example
 //!
 //! This section presents a minimal application built on top of `msp430-rt`.
@@ -113,12 +119,6 @@
 //! app: ELF 32-bit LSB executable, TI msp430, version 1 (embedded), statically linked, not stripped
 //! ```
 //!
-//! By default, the linker will check that the address after the vector table is 0x10000 to
-//! ensure that the vector table is placed correctly. For special cases like bootloader
-//! setups, you might want to place the vector table somewhere else. For theses cases,
-//! you can re-configure the expected end address by setting `__VECTOR_END_ADDR` in your
-//! `memory.x` file.
-//!
 //! # Optional features
 //!
 //! ## `device`