documentation cleanup

doc/gameid.md

@@ -2,11 +2,11 @@
 
 ## minetest versions >= 5.7 
 
-simply returns `minetest.get_game_info().id`  
+simply returns `core.get_game_info().id`  
 
 ## minetest versions < 5.7
 
 approximates the gameid value via a hardcoded table of gameid =\> modname,
-and then checks via `minetest.get_modpath()`. If it fails, it falls 
+and then checks via `core.get_modpath()`. If it fails, it falls 
 back to using `xcompat_unknown_gameid` as the id. See the chart in the
 readme for which games are supported

doc/materials.md

@@ -22,5 +22,5 @@ would closest represent the `steel_ingot` material in the current game.
 The `/src/materials/mineclonia.lua` file shows what the keys of
 `xcompat.materials` resolve to when playing Mineclonia, such as
 `xcompat.materials.steel_ingot` resolving to `mcl_core:iron_ingot`, and
-`xcompat.materials.mesa_crystal` resolving to `mcl_redstone:redstone` if
+`xcompat.materials.mese_crystal` resolving to `mcl_redstone:redstone` if
 supported.

doc/sounds.md

@@ -6,7 +6,7 @@
 You can do this by using a custom field in your node def instead of the `sounds` key.
 
 ```lua
-minetest.register_node(nodename, {
+core.register_node(nodename, {
     ...
     _sound_def = {
         key = "",
@@ -26,7 +26,7 @@ where:
 add this mod to your mod.confs depends and directly call the `sound_api` as follows
 
 ```lua
-minetest.register_node(nodename, {
+core.register_node(nodename, {
     ...
     sounds = xcompat.sounds.node_sound_stone_defaults(input)
     ...

doc/stairs.md

@@ -26,5 +26,5 @@ end
 ```
 
 that way in the future nothing will break when support is 
-added and at your convince the first part of the if can be 
-removed
+added and the first part of the if can be 
+removed at your convenience