diff --git a/docs/modular-steps-management.md b/docs/modular-steps-management.md
index 504742c64..c7f703f49 100644
--- a/docs/modular-steps-management.md
+++ b/docs/modular-steps-management.md
@@ -2,14 +2,14 @@
## Usage
-> After their first authentication in the app, every candidate has to do his **sign up** and his **onboarding**. The steps that compose the **sign up** and the **administration** section of the onboarding are either:
->
-> - Forms (identification, medical information, etc.)
-> - Documents to sign (general conditions, charts, regulations, etc.)
->
-> All the sections are modular: you can add, update, delete and order them as you wish.
->
-> This documentation explains how to manage these steps.
+After their first authentication in the app, every candidate has to do his **sign up** and his **onboarding**. The steps that compose the **sign up** and the **administration** section of the onboarding are either:
+
+- Forms (identification, medical information, etc.)
+- Documents to sign (general conditions, charts, regulations, etc.)
+
+All the sections are modular: you can add, update, delete and order them as you wish.
+
+This documentation explains how to manage these steps.
## Create your step child object
@@ -29,10 +29,10 @@
## Settings for a `form` step
-> In the step object you have created, 2 attributes must be filled:
->
-> 1. Subtype
-> 2. Form
+In the step object you have created, 2 attributes must be filled:
+
+1. Subtype
+2. Form
### Description
diff --git a/docs/object-child-creation.md b/docs/object-child-creation.md
index 01eee7e91..3fdf66143 100644
--- a/docs/object-child-creation.md
+++ b/docs/object-child-creation.md
@@ -2,14 +2,14 @@
## Usage
-> Objects of the Admin can be configured :
->
-> - By setting particular **attributes** to the object
-> - By associating **children** to the object
->
-> Children can be added, deleted, reordered in the list. Also, it's possible to configure it in a special way for the parent object, by setting children attributes for all the children.
->
-> This documentation explains how to associate a child to a parent object.
+Objects of the Admin can be configured :
+
+- By setting particular **attributes** to the object
+- By associating **children** to the object
+
+Children can be added, deleted, reordered in the list. Also, it's possible to configure it in a special way for the parent object, by setting children attributes for all the children.
+
+This documentation explains how to associate a child to a parent object.
### Create a new object for your child in the admin
@@ -32,9 +32,9 @@
- Select your step object in the select input
- Click on "ADD"
-> Your step is then related to its parent. You can see it in the _Children_ section of the parent's object. There, you can now:
->
-> - Delete the child from its parent (the actual object of your child will not be deleted).
-> - Reorder it in the children's list, by dragging it to the place you want.
-> - Update its original settings by clicking on the eye icon of its reference (redirection to object edit page of the child).
->
+Your step is then related to its parent. You can see it in the _Children_ section of the parent's object. There, you can now:
+
+- Delete the child from its parent (the actual object of your child will not be deleted).
+- Reorder it in the children's list, by dragging it to the place you want.
+- Update its original settings by clicking on the eye icon of its reference (redirection to object edit page of the child).
+
diff --git a/docs/object-creation.md b/docs/object-creation.md
index fc6e26744..6699ec159 100644
--- a/docs/object-creation.md
+++ b/docs/object-creation.md
@@ -2,17 +2,17 @@
## Usage
-> Elements of the app are managed through objects in _Admin_.
+Elements of the app are managed through objects in _Admin_.
-> Objects of the Admin are first created and defined:
->
-> - By their **title**,
-> - By their **type**.
+Objects of the Admin are first created and defined:
-> Then it can be configured through:
->
-> - Attributes,
-> - Children.
+- By their **title**,
+- By their **type**.
+
+Then it can be configured through:
+
+- Attributes,
+- Children.
> This documentation explains how to create an object.
@@ -49,10 +49,10 @@
- Three main objects define the major steps of the onboarding : _Toad_, _Administration_, _Piscine_.
- _Administration_ contains modular steps: _Additional Informations_, _Chart 01_, etc.
-> The child object is then available in the _Admin_. It can be found in the section of its type or thanks to the search bar of the cursus object's page.
+The child object is then available in the _Admin_. It can be found in the section of its type or thanks to the search bar of the cursus object's page.
+
+More information is available:
-> More information is available:
->
-> - for setting attributes of an object: (soon available)
-> - for setting children of an object: [Child object creation](object-child-creation.md)
-> - for creation of modular steps in Sign up and onboarding's Administration object: [Modular step management](modular-steps-management.md)
+- for setting attributes of an object: (soon available)
+- for setting children of an object: [Child object creation](object-child-creation.md)
+- for creation of modular steps in Sign up and onboarding's Administration object: [Modular step management](modular-steps-management.md)