Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix a couple typos in case study intro paragraph

Browse source
This commit is contained in:
Denver Gingerich 2014-11-07 10:50:14 -05:00
parent a94763abe4
commit 4bf096baa2
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
enforcement-case-studies.tex
View file

@ -266,7 +266,7 @@ However, in the experience of the two primary community-oriented enforcers,
Conservancy and the FSF, such CCS results routinely fix the description of
``barely complies with GPL's requirements''. To use an academic analogy:
while a ``C'' is certainly a passing grade, any instructor prefers to
disseminate to the class a exemplar sample that earned an ``A''.
disseminate to the class an exemplar sample that earned an ``A''.
Fortunately, thanks in large part to the FSF's
``Respects Your Freedom'' (RYF) certification campaign\footnote{\href{RYF is
@ -285,7 +285,7 @@ Specifically, this chapter discusses the purchase, CCS provision, and a
step-by-step build and installation analysis of a specific, physical,
embedded electronics product. The product in question is
\href{https://www.thinkpenguin.com/gnu-linux/free-software-wireless-n-broadband-router-gnu-linux-tpe-nwifirouter}{the
``TPE-NWIFIROUTER'' wireless router by ThinkPenguin}\footnote{The FSF of
``TPE-NWIFIROUTER'' wireless router by ThinkPenguin}.\footnote{The FSF of
course performed a thorough CCS check as part of the certification process.
The analysis discussed herein was independently performed by Software
Freedom Conservancy without reviewing any findings of the FSF, and thus the