intro: Fix trivial nits
cover intro: Fix trivial nits
This patchset fixes trivial nits in intro chapter, which I found while translating it.
SeongJae Park (2):
intro: Fix a wrong opening quote ('' -> ``)
intro: Add missed unbreakable spaces
intro/intro.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Signature · 1 line
2.17.1
PATCH 1/2 intro: Fix a wrong opening quote ('' -> ``)
Closing quote ('') is used in place of opening quote for a sentence. This commit fixes it.
Signed-off-by SeongJae Park <[email protected]>
--- intro/intro.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
intro/intro.tex +1 -1
@@ -155,7 +155,7 @@ as discussed in \cref{sec:cpu:Hardware Free Lunch?}. how could a large number of open-source projects, ranging from Apache to MySQL to the Linux kernel, have managed to master it? - A better question might be: ''Why is parallel programming {\em + A better question might be: ``Why is parallel programming {\em perceived} to be so difficult?'' To see the answer, let's go back to the year 1991. Paul McKenney was walking across the parking lot to Sequent's
Signature · 1 line
2.17.1
PATCH 2/2 intro: Add missed unbreakable spaces
In reply to SeongJae ParkThis commit adds missed unbreakable spaces ('~') in the intro chapter.
Signed-off-by SeongJae Park <[email protected]>
--- intro/intro.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
intro/intro.tex +2 -2
@@ -634,7 +634,7 @@ It should therefore be no surprise to see similar tradeoffs appear in the field of parallel computing. This tradeoff is shown schematically in \cref{fig:intro:Tradeoff Between Productivity and Generality}. -Here, users~1, 2, 3, and 4 have specific jobs that they need the computer +Here, users~1, 2, 3, and~4 have specific jobs that they need the computer to help them with. The most productive possible language or environment for a given user is one that simply does that user's job, without requiring any programming,
@@ -673,7 +673,7 @@ Haskell, Prolog, or Snobol), as is shown by the circular region near the center of \cref{fig:intro:Tradeoff Between Productivity and Generality}. These languages can be considered to be general in the sense that they -are equally ill-suited to the jobs required by users~1, 2, 3, and 4. +are equally ill-suited to the jobs required by users~1, 2, 3, and~4. In other words, their generality comes at the expense of decreased productivity when compared to domain-specific languages and environments.
Signature · 1 line
2.17.1
Quoted 6 lines · SeongJae Park
This patchset fixes trivial nits in intro chapter, which I found while translating it.
SeongJae Park (2):
intro: Fix a wrong opening quote ('' -> ``)
intro: Add missed unbreakable spaces
Good eyes! Queued and pushed, thank you!
Thanx, Paul
Quoted 6 lines
intro/intro.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)Signature · 1 line
2.17.1