diff --git a/docs/2_1_common_api.adoc b/docs/2_1_common_api.adoc
index 51560a989..1774b1e72 100644
--- a/docs/2_1_common_api.adoc
+++ b/docs/2_1_common_api.adoc
@@ -296,8 +296,9 @@ If one of the functions returns `fmi2Error`,
 it can be tried to restart the simulation from a formerly stored FMU state by calling `fmi2SetFMUstate`.
 This can be done if the capability flag `canGetAndSetFMUstate` is true and
 `fmi2GetFMUstate` was called before in non-erroneous state.
+It is also possible to reset the instance of the FMU by calling `fmi2Reset`.
 footnote:[Typically, `fmi2Error` return is for non-numerical reasons, like "disk full".
-There might be cases where the environment can fix such errors (eventually with the help oft the user),
+There might be cases where the environment can fix such errors (eventually with the help of the user),
 and then simulation can continue at the last consistent state defined with `fmi2SetFMUstate`.] +
 Further processing is possible after this call;
 especially other FMU instances are not affected.