From 3675fbd2e919198580c73c7ae16dd24610ba728b Mon Sep 17 00:00:00 2001
From: barinek <barinek@initialcapacity.io>
Date: Tue, 3 May 2022 13:49:16 -0600
Subject: [PATCH] minor update - code review or pull request workflow

---
 README.md   | 6 +++---
 pairing.tex | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 8b1e480..43599cd 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,6 @@
 # Why pairing is faster
 
-A paper proving that pairing is faster than pull requests.
+A paper proving that pairing is faster than a code review or pull request workflow.
 
 Download the [latest draft](https://github.com/initialcapacity/why-pairing-is-faster/releases/latest/download/why-pairing-is-faster.pdf)
 of the paper.
@@ -18,8 +18,8 @@ We complete more features faster by pairing because the code reviews happen in p
 ## Summary 
 
 When paring, dependencies between stories in a backlog have less of an impact on team velocity.
-The impact of dependencies is much higher in a pull request workflow, meaning stories must be highly parallelizable
-to achieve the same productivity.
+The impact of dependencies is much higher in a code review or pull request workflow, meaning stories must be
+highly parallelizable to achieve the same productivity.
 
 ## Simulator
 
diff --git a/pairing.tex b/pairing.tex
index e57b301..af8e9ad 100644
--- a/pairing.tex
+++ b/pairing.tex
@@ -182,7 +182,7 @@
     \section{Summary}\label{sec:summary}
 
     When paring, dependencies between stories in a backlog have less of an impact on team velocity.
-    The impact of dependencies is much higher in a pull request workflow, meaning stories must be highly parallelizable
-    to achieve the same productivity.
+    The impact of dependencies is much higher in a code review or pull request workflow, meaning stories must be
+    highly parallelizable to achieve the same productivity.
 
 \end{document}