diff --git a/src/frontend/src/pages/Chapter/Chapter.data.tsx b/src/frontend/src/pages/Chapter/Chapter.data.tsx
index 795d3bc..9853722 100644
--- a/src/frontend/src/pages/Chapter/Chapter.data.tsx
+++ b/src/frontend/src/pages/Chapter/Chapter.data.tsx
@@ -36,6 +36,7 @@ import { data as pascalDataDeployContract } from '../Chapters/Pascal/ChapterDepl
 import { data as pascalDataFA12 } from '../Chapters/Pascal/ChapterFA12'
 import { data as pascalDataFA20 } from '../Chapters/Pascal/ChapterFA20'
 import { data as pascalDataFA20Operator } from '../Chapters/Pascal/ChapterFA20Operator'
+import { data as pascalDataFA20Hook } from '../Chapters/Pascal/ChapterFA20Hook'
 import { data as pascalDataFunctions } from '../Chapters/Pascal/ChapterFunctions'
 import { data as pascalDataInteractions } from '../Chapters/Pascal/ChapterInteractions'
 import { data as pascalDataInterop } from '../Chapters/Pascal/ChapterInterop'
@@ -220,7 +221,7 @@ export const chapterData = [
     pathname: '/pascal/chapter-fa2-hook',
     language: 'PascaLIGO',
     name: '30 - Pascal - FA2 Hook',
-    data: camelDataFA20Hook,
+    data: pascalDataFA20Hook,
   },
 
   {
@@ -494,10 +495,4 @@ export const chapterData = [
     name: '29 - Reason - FA2 Operator',
     data: reasonDataFA20Operator,
   },
-  {
-    pathname: '/reason/chapter-fa2-hook',
-    language: 'ReasonLIGO',
-    name: '30 - Reason - FA2 Hook',
-    data: camelDataFA20Hook,
-  },
 ]
diff --git a/src/frontend/src/pages/Chapters/Camel/ChapterPreprocessor/course.md b/src/frontend/src/pages/Chapters/Camel/ChapterPreprocessor/course.md
index 04290ff..c71236e 100644
--- a/src/frontend/src/pages/Chapters/Camel/ChapterPreprocessor/course.md
+++ b/src/frontend/src/pages/Chapters/Camel/ChapterPreprocessor/course.md
@@ -1,6 +1,6 @@
 # Chapter 27 : Preprocessor
 
-<dialog character="mechanics"></dialog>
+<dialog character="mechanics">Now that you are producing a lot of code it could be relevant to split the code and work with many files including each other.</dialog>
 
 Instead of writing the LIGO code in a single file, it is possible to split the code into different files and include some external code into our file. The pre-processor is responsible for handling code inclusion. While working with multiple files we may encounter a problem of cyclic inclusion. To prevent such situation some pre-processor commands are available.
 
diff --git a/src/frontend/src/pages/Chapters/Pascal/ChapterPreprocessor/course.md b/src/frontend/src/pages/Chapters/Pascal/ChapterPreprocessor/course.md
index 788ef7c..1418dec 100644
--- a/src/frontend/src/pages/Chapters/Pascal/ChapterPreprocessor/course.md
+++ b/src/frontend/src/pages/Chapters/Pascal/ChapterPreprocessor/course.md
@@ -1,6 +1,6 @@
 # Chapter 27 : Preprocessor
 
-<dialog character="mechanics"></dialog>
+<dialog character="mechanics">Now that you are producing a lot of code it could be relevant to split the code and work with many files including each other.</dialog>
 
 Instead of writing the LIGO code in a single file, it is possible to split the code into different files and include some external code into our file. The pre-processor is responsible for handling code inclusion. While working with multiple files we may encounter a problem of cyclic inclusion. To prevent such situation some pre-processor commands are available.
 
diff --git a/src/frontend/src/pages/Chapters/Reason/ChapterPreprocessor/course.md b/src/frontend/src/pages/Chapters/Reason/ChapterPreprocessor/course.md
index 52d910c..7641b92 100644
--- a/src/frontend/src/pages/Chapters/Reason/ChapterPreprocessor/course.md
+++ b/src/frontend/src/pages/Chapters/Reason/ChapterPreprocessor/course.md
@@ -1,6 +1,6 @@
 # Chapter 27 : Preprocessor
 
-<dialog character="mechanics"></dialog>
+<dialog character="mechanics">Now that you are producing a lot of code it could be relevant to split the code and work with many files including each other.</dialog>
 
 Instead of writing the LIGO code in a single file, it is possible to split the code into different files and include some external code into our file. The pre-processor is responsible for handling code inclusion. While working with multiple files we may encounter a problem of cyclic inclusion. To prevent such situation some pre-processor commands are available.