25/66: icse-2022: Final (?) tweaks.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository maintenance.

commit 7dc47b1a61fa4d2fdee2621059b8761518ec4daa
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Tue Aug 31 12:27:49 2021 +0200

    icse-2022: Final (?) tweaks.
---
 doc/icse-2022/supply-chain.skb | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/icse-2022/supply-chain.skb b/doc/icse-2022/supply-chain.skb
index 03d4efb..2bbc6e1 100644
--- a/doc/icse-2022/supply-chain.skb
+++ b/doc/icse-2022/supply-chain.skb
@@ -256,7 +256,7 @@ of a Git checkout authentication mechanism and ,(numref 
:text [Section]
 while ,(numref :text [Section] :ident "mirrors") focuses on the related
 risk of distributing stale revisions.  In ,(numref :text [Section]
 :ident "implementation") we provide key elements of the implementation
-and report on our early experience.  Last, ,(numref :text [Section]
+and report on our experience.  Last, ,(numref :text [Section]
 :ident "related") compares to related work and ,(numref :text [Section]
 :ident "conclusion") concludes.]))
    
@@ -290,7 +290,7 @@ rollbacks]): because build results are kept in the store by 
default, any
 new deployment, of individual packages or whole systems, can be rolled
 back ,(ref :bib '(dolstra2004:nix courtes2013:functional)).  Its ability
 to reproduce software environments, bit for bit, at different points in
-time and on different machines, make it a tool of choice in support of
+time and on different machines, makes it a tool of choice in support of
 reproducible computational experiments and software engineering ,(ref
 :bib 'hinsen2020:staged-computation).])
 
@@ -335,7 +335,7 @@ such that it emits malicious code when it recognizes 
specific patterns
 of source code.  This attack can be undetectable.  What makes such
 attacks possible is that users and distributions rely on opaque binaries
 at some level to “bootstrap” the entire package dependency graph.])
-      (p [In 2017, Jan Nieuwenhuizen ,(it [et al.]) sought to address
+      (p [In 2017, Nieuwenhuizen ,(it [et al.]) sought to address
 this forty-year-old problem at its root: by ensuring no opaque binaries
 appear in the package dependency graph—no less ,(ref :bib
 'janneke:mes-web).  To that end, Nieuwenhuizen developed GNU Mes, a