From c16512e81b2c82933cd747a07c6af54a0edfb68c Mon Sep 17 00:00:00 2001
From: sjcjoosten <sjcjoosten+github@gmail.com>
Date: Fri, 7 Jun 2024 15:01:49 -0500
Subject: [PATCH] minor textual edits

---
 2022Migration/articleMigrationRaMiCS.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/2022Migration/articleMigrationRaMiCS.tex b/2022Migration/articleMigrationRaMiCS.tex
index b0c4b61..dc4da69 100644
--- a/2022Migration/articleMigrationRaMiCS.tex
+++ b/2022Migration/articleMigrationRaMiCS.tex
@@ -657,7 +657,7 @@ \subsection{Generating a migration script}
    Let $\pair{\dataset}{\schema}$ be the existing system.
    Let $\pair{\dataset'}{\schema'}$ be the desired system in its initial state.
 \begin{enumerate}
-\item We take a disjoint union of the data sets by relabeling relation names, so the migration script can refer to relations from both systems:
+\item We take a disjoint union of the data sets by relabeling relation symbols, so the migration script can refer to relations from both systems:
    \begin{align}
       \dataset_\migrsys={}&\overleftarrow{\dataset}\cup\overrightarrow{\dataset'}
    \end{align}
@@ -733,7 +733,7 @@ \subsection{Generating a migration script}
      \transactions_2\ =\ \{{\tt fixed}_u\mapsfrom\lambda\dataset.~\cmpl{\viol{u}{\dataset} \cup \pop{{\tt fixed}_u}{\dataset}}\mid u\in\overrightarrow{\rules_{\schema'}-\rules_{\schema}}\}\label{eqn:enforceForRules}
      % Opmerking van SJC: de {\tt fixed}_u aan de rechterkant is nodig om aan (\ref{eqn:transaction}) te voldoen.
    \end{equation}
-\item\label{step5} To signal users that there are violations that need to be fixed, we generate a business constraint for each new blocking invariant $u$:
+\item\label{step5} To signal users that there are violations that need to be fixed, we generate a business constraint for each new blocking invariant denoted by $u$:
 % \begin{verbatim}
 %    ROLE User MAINTAINS TOTr
 %    RULE TOTr : I |- new.r;new.r~
@@ -750,7 +750,7 @@ \subsection{Generating a migration script}
       &\mid u\in\overrightarrow{\rules_{\schema'}-\rules_{\schema}}\}\notag
    \end{align}
    In some cases, a migration engineer can invent ways to satisfy these invariants automatically.
-   For this purpose, the generator must produce source code (as opposed to compiled code) to allow the migration engineer
+   This is one of the places where it is useful for the generator to produce source code (as opposed to compiled code) to allow the migration engineer
    to replace a business constraint with transactional invariants of her own making.
    After all violations are fixed, i.e. when equation~\ref{eqn:readyForMoC} is satisfied,
    the migration engineer can switch the ingress to the desired system.