diff --git a/CHANGES/1264.doc.rst b/CHANGES/1264.doc.rst
new file mode 100644
index 00000000..b5cc6f82
--- /dev/null
+++ b/CHANGES/1264.doc.rst
@@ -0,0 +1 @@
+Supplemented a section Finite State Machine in Migration FAQ
diff --git a/docs/migration_2_to_3.rst b/docs/migration_2_to_3.rst
index 9b17710e..8a42fa5e 100644
--- a/docs/migration_2_to_3.rst
+++ b/docs/migration_2_to_3.rst
@@ -112,10 +112,13 @@ Finite State machine
 - State filter will no more added to all handlers, you will need to specify state if you want
 - Added possibility to change FSM strategy, for example if you want to control state
   for each user in chat topics instead of user in chat you can specify it in the Dispatcher.
-- Now :class:`aiogram.fsm.state.State` and :class:`aiogram.fsm.state.StateGroup` don't have helper methods like :code:`set()`, :code:`next()`, etc. 
+- Now :class:`aiogram.fsm.state.State` and :class:`aiogram.fsm.state.StateGroup` don't have helper
+  methods like :code:`.set()`, :code:`.next()`, etc.
 
-  Instead of this you should set states by passing them directly to :class:`aiogram.fsm.context.FSMContext` (:ref:`Read more » <finite-state-machine>`)
-- State proxy is deprecated, you should update the state data by calling :code:`state.set_data()` and :code:`state.get_data()` respectively.
+  Instead of this you should set states by passing them directly to
+  :class:`aiogram.fsm.context.FSMContext` (:ref:`Read more » <Finite State Machine>`)
+- State proxy is deprecated, you should update the state data by calling
+  :code:`state.set_data(...)` and :code:`state.get_data()` respectively.
 
 
 Sending Files