some correction

src/frontend/src/pages/Chapters/Camel/ChapterFA20Hook/course.md

@@ -4,7 +4,7 @@
 
 ## ... in the previous episode
 
-The FA2 standard proposes a _unified token contract interface_ that accommodates all mentioned concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
+The FA2 standard proposes a _unified token contract interface_ that accommodates fungibility and multiple asset concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
 
 The FA2 interface formalizes a standard way to design tokens and thus describes a list of entry points (that must be implemented) and data structures related to those entry points.
 

src/frontend/src/pages/Chapters/Camel/ChapterFA20Operator/course.md

@@ -4,7 +4,7 @@
 
 ## Definition
 
-The FA2 standard proposes a _unified token contract interface_ that accommodates all mentioned concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
+The FA2 standard proposes a _unified token contract interface_ that accommodates fungibility and multiple asset concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
 
 In this chapter we will focus on _Operators_ and _Permissions_.
 

src/frontend/src/pages/Chapters/Pascal/ChapterFA20Hook/course.md

@@ -4,7 +4,7 @@
 
 ## ... in the previous episode
 
-The FA2 standard proposes a _unified token contract interface_ that accommodates all mentioned concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
+The FA2 standard proposes a _unified token contract interface_ that accommodates fungibility and multiple asset concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
 
 The FA2 interface formalizes a standard way to design tokens and thus describes a list of entry points (that must be implemented) and data structures related to those entry points.
 

src/frontend/src/pages/Chapters/Pascal/ChapterFA20Operator/course.md

@@ -4,7 +4,7 @@
 
 ## Definition
 
-The FA2 standard proposes a _unified token contract interface_ that accommodates all mentioned concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
+The FA2 standard proposes a _unified token contract interface_ that accommodates fungibility and multiple asset concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
 
 In this chapter we will focus on _Operators_ and _Permissions_.
 

src/frontend/src/pages/Chapters/Reason/ChapterFA20/course.md

@@ -36,8 +36,6 @@ In addition to the FA2 interface, the FA2 standard provides helper functions to
 
 Token contract implementing the FA2 standard MUST have the following entry points.
 
-TODO should be renamed fa2_entry_points
-
 ```
 type parameter =
 | Transfer(transferParameter)
@@ -47,9 +45,12 @@ type parameter =
 | Token_metadata_registry(tokenMetadataRegistryParameter)
 ```
 
+<!-- prettier-ignore -->⚠️ Notice that the type _parameter_ describes all FA2 entry points (and should be renamed *fa2\_entry\_points* in the next release of the FA2 reasonML implementation)
+
+
 ### Balance of
 
-The FA2 client (contracts using our token) may need to know the balance of a owner. The FA2 standard specifies an entry point _Balance of_ which use a callback in order to send the balance information to the calling contract.
+The FA2 client (contracts using our token) may need to know the balance of an owner. The FA2 standard specifies an entry point _Balance of_ which use a callback in order to send the balance information to the calling contract.
 
 <!-- prettier-ignore -->FA2 token contracts MUST implement the _Balance of_ entry point which gets the balance of multiple account/token pairs (because FA2 supports multiple token).
 

src/frontend/src/pages/Chapters/Reason/ChapterFA20Operator/course.md

@@ -4,7 +4,7 @@
 
 ## Definition
 
-The FA2 standard proposes a _unified token contract interface_ that accommodates all mentioned concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
+The FA2 standard proposes a _unified token contract interface_ that accommodates fungibility and multiple asset concerns. It aims to provide significant expressivity to contract developers to create new types of tokens while maintaining a common interface standard for wallet integrators and external developers.
 
 In this chapter we will focus on _Operators_ and _Permissions_.