Wordsmithing and typo fixes.
This commit is contained in:
		
							parent
							
								
									07828daf38
								
							
						
					
					
						commit
						8399b0a796
					
				
					 1 changed files with 9 additions and 9 deletions
				
			
		|  | @ -1021,15 +1021,15 @@ Thus, users are explicitly given the freedom to run by \S 0. | |||
| 
 | ||||
| The bulk of \S 0 not yet discussed gives definitions for other terms used | ||||
| throughout.  The only one worth discussing in detail is ``work based on | ||||
| the Program.''  The reason this definition is particularly interesting is | ||||
| the Program''.  The reason this definition is particularly interesting is | ||||
| not for the definition itself, which is rather straightforward, but | ||||
| because it clears up a common misconception about the GPL\@. | ||||
| 
 | ||||
| The GPL is often mistakenly criticized because it fails to give a | ||||
| definition of ``derivative work.''  In fact, it would be incorrect and | ||||
| definition of ``derivative work''.  In fact, it would be incorrect and | ||||
| problematic if the GPL attempted to define this.  A copyright license, in | ||||
| fact, has no control over what may or may not be a derivative work.  This | ||||
| matter is left up to copyright law, not the licenses that utilize it. | ||||
| matter is left up to copyright law and the courts --- not the licenses that utilize it. | ||||
| 
 | ||||
| It is certainly true that copyright law as a whole does not propose clear | ||||
| and straightforward guidelines for what is and is not a derivative | ||||
|  |  | |||
		Loading…
	
	Add table
		
		Reference in a new issue
	
	 Bradley M. Kuhn
						Bradley M. Kuhn