Correct spelling mistakes

chapters/creating_textures.md

@@ -58,7 +58,7 @@ learning curve as lots of its features are hidden away.
 
 ## Common Mistakes
 
-### Blurred textures through incorrect tools
+### Blurred textures through usage of incorrect tools
 
 For the most part, you want to manipulate pixels on an individual basis.
 The tool for this in most editors is the pencil tool.

chapters/lua.md

@@ -145,7 +145,7 @@ end
 {% endhighlight %}
 
 That example generates a random number between 1 and 100. It then prints
-"Woohoo!" if that number is bigger than 50, overwise it prints "No!".
+"Woohoo!" if that number is bigger than 50, otherwise it prints "No!".
 What else can you get apart from '>'?
 
 ### Logical Operators
@@ -278,7 +278,7 @@ two()
 {% endhighlight %}
 
 Nil means **not initalised**. The variable hasn't been assigned a variable yet,
-doesn't exist or has been uninitalised (ie: set to nil)
+doesn't exist or has been uninitialised (ie: set to nil)
 
 The same goes for functions. Functions are variables of a special type.
 You should make functions as local as much as possible,

chapters/node_drawtypes.md

@@ -111,7 +111,8 @@ minetest.register_node("myair:air", {
 	</figcaption>
 </figure>
 
-These nodes are complete liquid nodes, the liquid flows outwards from position using the flowing liquid drawtype.
+These nodes are complete liquid nodes, the liquid flows outwards from position
+using the flowing liquid drawtype.
 For each liquid node you should also have a flowing liquid node.
 
 {% highlight lua %}

chapters/nodes_items_crafting.md

@@ -62,7 +62,7 @@ minetest.register_craftitem("mymod:diamond_fragments", {
 
 Item definitions like seen above are usually made up of an unique
 [item string](#item-strings) and a definition table. The definition table
-contains attributes which affect the behavour of the item.
+contains attributes which affect the behaviour of the item.
 
 ### Foods
 

chapters/releasing.md

@@ -23,7 +23,9 @@ In this chapter we will find out how to publish a mod so that other users can us
 You need to specify a license for your mod.
 **Public domain is not a valid licence**, as the definition varies in different countries.
 
-First thing you need to note is that your code and your art need different types of protection.
+First thing you need to note is that your code and your art need different things from
+the license they use. Creative Commons licenses shouldn't be used with source code,
+but rather with artistic works such as images, text and meshes.
 
 You are allowed any license, however mods which disallow derivatives are banned from the forum.
 (Other developers must be able to take your mod, modify it, and release it again.)
@@ -34,7 +36,8 @@ This is a common license combination in the Minetest community, as it is what
 Minetest and minetest_game use.
 You license your code under LGPL 2.1 and your art under CC-BY-SA.
 
-* If someone modifies your mod, they must give their version the same license
+* Anyone can modify, redistribute and sell modified or unmodified versions.
+* If someone modifies your mod, they must give their version the same license.
 * Your copyright notice must be kept.
 
 Add this copyright notice to your README.txt, or as a new file called LICENSE.txt
@@ -93,7 +96,7 @@ Example:
 	Adds magic, rainbows and other special things.
 
 	Version: 1.1
-	Licence: LGPL 2.1 or later
+	License: LGPL 2.1 or later
 
 	Dependencies: default mod (found in minetest_game)
 
@@ -105,7 +108,7 @@ Example:
 	Unzip the archive, rename the folder to to modfoldername and
 	place it in minetest/mods/minetest/
 
-	(  Linux: If you have a linux system-wide installation place
+	(  GNU/Linux: If you use a system-wide installation place
 		it in ~/.minetest/mods/minetest/.  )
 
 	(  If you only want this to be used in a single world, place
@@ -133,7 +136,7 @@ Uploading
 ---------
 
 In order for a potential user to download your mod, you need to upload it to somewhere
-which is publically accessible.\\
+which is publicly accessible.\\
 I will outline several methods you can use, but really you should use the one that works
 best for you, as long as it mets these requirements:\\
 (and any other requirements which may be added by forum moderators)
@@ -145,7 +148,7 @@ best for you, as long as it mets these requirements:\\
 
 ### Github, or another VCS
 
-It is recommended that you use Version Control System for the following reasons:
+It is recommended that you use a Version Control System for the following reasons:
 
 * Allows other developers to submit changes (easily).
 * Allows the code to be previewed before downloading.
@@ -153,7 +156,7 @@ It is recommended that you use Version Control System for the following reasons:
 
 However, such systems may be hard to understand when you first start out.
 
-The majority of Minetest developers use Github as a website to host their code,
+The majority of Minetest developers use GitHub as a website to host their code,
 however that doesn't matter that much.
 
 * [Using Git](http://git-scm.com/book/en/v1/Getting-Started) - Basic concepts. Using the command line.
@@ -210,7 +213,7 @@ Here is an example. The Minetest forum uses bbcode for formating.
 	See download attached.
 
 	[b]Version:[/b] 1.1
-	[b]Licence:[/b] LGPL 2.1 or later
+	[b]License:[/b] LGPL 2.1 or later
 
 	Dependencies: default mod (found in minetest_game)
 
@@ -221,7 +224,7 @@ Here is an example. The Minetest forum uses bbcode for formating.
 	Unzip the archive, rename the folder to to modfoldername and
 	place it in minetest/mods/minetest/
 
-	(  Linux: If you have a linux system-wide installation place
+	(  GNU/Linux: If you use a system-wide installation place
 		it in ~/.minetest/mods/minetest/.  )
 
 	(  If you only want this to be used in a single world, place