doc correction

Author: franckgaga

docs/src/manual.md

@@ -60,8 +60,7 @@ We first need to construct a [`LinModel`](@ref) objet with [`setop!`](@ref) to h
 operating points:
 
 ```@example 1
-using ControlSystemsBase
-using ModelPredictiveControl
+using ModelPredictiveControl, ControlSystemsBase
 sys = [ tf(1.90, [18, 1]) tf(1.90, [18, 1]);
         tf(-0.74,[8, 1])  tf(0.74, [8, 1]) ]
 Ts = 4.0
@@ -117,11 +116,11 @@ t_data = Ts*(0:(size(y_data,2)-1))
 nothing # hide
 ```
 
-The [`LinMPC`](@ref) objects are also callable to provide an alternative syntax for
-the [`moveinput!`](@ref) method. Calling [`updatestate!`](@ref) on the `mpc` object updates
-its internal state for the *NEXT* control period (this is by design, see
-[State Estimators](@ref) for the justification). That is why the call is done at the
-end of the `for` loop. The same logic applies for `model`.
+The [`LinMPC`](@ref) objects are also callable as an alternative syntax for
+[`moveinput!`](@ref). Calling [`updatestate!`](@ref) on the `mpc` object updates its
+internal state for the *NEXT* control period (this is by design, see
+[State Estimators](@ref) for justifications). That is why the call is done at the end of the
+`for` loop. The same logic applies for `model`.
 
 Lastly, we plot the closed-loop test with the `Plots` package:
 

docs/src/public/predictive_control.md

@@ -11,7 +11,7 @@ predictions. The default [`LinMPC`](@ref) estimator is a [`SteadyKalmanFilter`](
 current model mismatch estimation is constant in the future (same approach than dynamic
 matrix control, DMC).
 
-## Abstract Types
+## PredictiveController
 
 ```@docs
 PredictiveController

docs/src/public/sim_model.md

@@ -11,7 +11,7 @@ simulators by calling [`evaloutput`](@ref) and [`updatestate!`](@ref) methods on
 states `x` are stored inside [`SimModel`](@ref) objects. Use [`setstate!`](@ref) method
 to manually modify them.
 
-## Abstract Types
+## SimModel
 
 ```@docs
 SimModel

docs/src/public/state_estim.md

@@ -23,7 +23,7 @@ sometimes slightly more accurate.
 
 The predictor form comes in handy for control applications since the estimations come after
 the controller computations, without introducing any additional delays. Moreover, the
-[`moveinput!`](@ref) method of the predictive controller does not automatically update the
+[`moveinput!`](@ref) method of the predictive controllers does not automatically update the
 estimates with [`updatestate!`](@ref). This allows applying the calculated inputs on the
 real plant before starting the potentially expensive estimator computations (see
 [Manual](@ref) for examples).
@@ -32,7 +32,7 @@ real plant before starting the potentially expensive estimator computations (see
     All the estimators support measured ``\mathbf{y^m}`` and unmeasured ``\mathbf{y^u}``
     model outputs, where ``\mathbf{y}`` refers to all of them.
 
-## Abstract Types
+## StateEstimator
 
 ```@docs
 StateEstimator