Copyleft/guide Changeset - 62c0fe86a619

Changeset - 62c0fe86a619

Parent rev.

Child rev.

[Not reviewed]

0 1 0

Denver Gingerich - 9 years ago 2014-11-07 16:11:41
denver@ossguy.com

Fix more typos in "Root Filesystem..." section

1 file changed with 3 insertions and 3 deletions:

enforcement-case-studies.tex

0 comments (0 inline, 0 general)

enforcement-case-studies.tex

➞

Show inline comments

@@ ... @@
 you use this configuration.
 \end{quotation}
 This instruction actually goes above and beyond the requirements of GPL\@.
 Specifically, the instruction guides users in their first step toward
 exercising the freedom to modify the software.  While the GPL does contain
 requirements that facility the freedom to modify (such as ensuring the CCS is
 in the ``preferred form \ldots for making modifications to it'' form, it
 requirements that facilitate the freedom to modify (such as ensuring the CCS is
 in the ``preferred form \ldots for making modifications to it'' form), it
 does not require that you write specific instructions explaining how
 modifications might be undertaken.  This instruction therefore exemplifies
 the exceptional quality of this particular CCS\@.
 %FIXME: add a \hyperref to some ``preferred for for modification'' stuff above.
@@ ... @@
 kept a
 \href{https://gitorious.org/copyleft-org/tutorial/source/master:enforcement-case-studies_log-output/thinkpenguin_librecmc-complete.log}{full
   log of the build}, which is not included herein due its size (approximately
 .2K of text).
 \label{thinkpenguin-main-build}
-Upon competition of the ``make'' process, the investigator immediately found
+Upon completion of the ``make'' process, the investigator immediately found
 (almost to his surprise) several large firmware files in the ``bin/ar71xx''
 directory.  Typically, this step in the CCS verification process is
 harrowing.  In most cases, the ``make'' step will fail due to a missing
 package or because toolchain paths are not setup correctly.
 From experience, the investigator is sure that ThinkPenguin's engineers did

0 comments (0 inline, 0 general)