worldedit_gui: Improve behaviour of all input fields

[worldedit.git] / Tutorial.md

diff --git a/Tutorial.md b/Tutorial.md
index abe554ad379bfcc79f7dae422255a6de3547ac6a..1ed399831ecdb0a1af6317c7954fda15be3f176f 100644 (file)
--- a/Tutorial.md
+++ b/Tutorial.md
@@ -107,7 +107,7 @@ Step 4: Other commands
 ----------------------\r
 ### Chat Commands\r
 \r
-There are many more commands than what is shown here. See the [Chat Commands Reference](Chat Commands.md) for a detailed list of them, along with descriptions and examples for every single one.\r
+There are many more commands than what is shown here. See the [Chat Commands Reference](ChatCommands.md) for a detailed list of them, along with descriptions and examples for every single one.\r
 \r
 If you're in-game and forgot how a command works, just use the `/help <command name>` command, without the first forward slash. For example, to see some information about the `//set <node>` command mentioned earlier, simply use `/help /set`.\r
 \r
@@ -115,6 +115,6 @@ A very useful command to check out is the `//save <schematic>` command, which ca
 \r
 ### WorldEdit GUI\r
 \r
-This only scratches the surface of what WorldEdit is capable of. Most of the functions in the WorldEdit GUI correspond to chat commands, and so the [Chat Commands Reference](Chat Commands.md) may be useful if you get stuck.\r
+This only scratches the surface of what WorldEdit is capable of. Most of the functions in the WorldEdit GUI correspond to chat commands, and so the [Chat Commands Reference](ChatCommands.md) may be useful if you get stuck.\r
 \r
 It is helpful to explore the various buttons in the interface and check out what they do. Learning the chat command interface is also useful if you use WorldEdit intensively - an experienced chat command user can usually work faster than an experienced WorldEdit GUI user.
\ No newline at end of file