From 112d56ae95bfddd6a3cd60bec413de44d046a732 Mon Sep 17 00:00:00 2001
From: Pierre Courtieu <Pierre.Courtieu@cnam.fr>
Date: Thu, 16 Jan 2025 09:49:30 +0100
Subject: [PATCH] Typos and formatting.

---
 DEV.md     | 17 +++++++++++++----
 INSTALL.md |  2 +-
 README.md  |  2 --
 3 files changed, 14 insertions(+), 7 deletions(-)

diff --git a/DEV.md b/DEV.md
index 28ee18e4..e9836194 100644
--- a/DEV.md
+++ b/DEV.md
@@ -1,6 +1,12 @@
-The fundamental principle is that the MASTER branch must remain compilable at all times and should never contain incomplete developments.
+The fundamental principle is that the MASTER branch must remain
+compilable at all times and should never contain incomplete
+developments.
 
-Development work on the master branch must be avoided. Instead, each feature or topic should have its own dedicated branch. Developers should create new branches as needed, and all work—including collaborative efforts—should occur within these topic-specific branches.
+Development work on the master branch must be avoided. Instead, each
+feature or topic should have its own dedicated branch. Developers
+should create new branches as needed, and all work—including
+collaborative efforts—should occur within these topic-specific
+branches.
 
 Before merging changes into master, ensure that your code:
 
@@ -10,7 +16,10 @@ Before merging changes into master, ensure that your code:
 -   Uses descriptive hypothesis names rather than auto-generated ones
 -   Meets all project quality standards
 
-When your changes are ready (such as a completed case study), you have two options:
+When your changes are ready (such as a completed case study), you have
+two options:
 
 1.  Submit a pull request for review
-2.  Merge directly into master after squashing your commits into meaningful, well-organized units (typically one or a few commits that clearly represent the changes)
+2.  Merge directly into master after squashing your commits into
+    meaningful, well-organized units (typically one or a few commits
+    that clearly represent the changes)
diff --git a/INSTALL.md b/INSTALL.md
index 1d7367e4..019e84be 100644
--- a/INSTALL.md
+++ b/INSTALL.md
@@ -1,7 +1,7 @@
 
 # Requirements
 
-- Coq 8.19 or 8.20 (including the executable `coqc`, `codep`, `coq_makefile`)
+- Coq 8.19 or 8.20 (including the executable `coqc`, `coqdep`, `coq_makefile`)
 - GNU `make`
 
 # Configuration
diff --git a/README.md b/README.md
index c92dccf7..e3235e78 100644
--- a/README.md
+++ b/README.md
@@ -106,5 +106,3 @@ A general description of the Pactole library and its use:
  Courtieu, Rieg, Tixeuil, and Urbain. *Swarms of Mobile Robots: Towards
    Versatility with Safety.* Leibniz Transactions on Embedded Systems (LITES), 8(2):02:1–
    02:36, 2022. [link](https://doi.org/10.4230/LITES.8.2.2)
-
-   02:36, 2022.
-- 
GitLab