fixing some syntax issues

Author: LichtHund

triumph-gui/4_x_x/1-started/creating-gui.md

@@ -13,15 +13,15 @@ Kotlin examples require the `dev.triumphteam:triumph-gui-<platform>kotlin:<versi
 
 # Starting
 
-To create a [GUI](/gui), we call the builder for the desired (Container Type)[/container-type]. This will return a GUI
+To create a [GUI](/gui), we call the builder for the desired [Container Type](/container-type). This will return a GUI
 builder.  
 The builder allows you to setup all the components as well as personalize how the GUI should function. Like for example
-setting custom (renderer)[/renderer]s.
+setting custom [renderer](/renderer)s.
 
 Let's create a GUI with a `1` row and an item the middle that sends the `player` a message when clicking.
 
 -+-  
-+Java+
++Java+  
 
 ```java
 final var gui = Gui.of(1)
@@ -41,7 +41,7 @@ gui.open(player);
 ```
 
 +++  
-+Kotlin+
++Kotlin+  
 ```kotlin
 val gui = buildGui {
     // If not set, defaults to chest - 1 row
@@ -67,5 +67,5 @@ gui.open(player)
 ```
 +++  
 -+-  
-Now that the GUI is created, we can dive into something more complex by utilizing (States)[/states].  
-We can continue onto the next example (here)[/using-states].
+Now that the GUI is created, we can dive into something more complex by utilizing [States](/states).  
+We can continue onto the next example [here](/using-states).

triumph-gui/4_x_x/1-started/updating-title.md

@@ -22,10 +22,10 @@ For that we need to create a state that is not in the same place as the opening
 command class.
 
 For this state it's nice to make it so it can only be updated if the clicks are higher than the stored value. Thankfully
-we can use a (StateMutationPolicy)[/mutation-policy] for that, so let's create a new one!
+we can use a [StateMutationPolicy](/mutation-policy) for that, so let's create a new one!
 
 -+-  
-+Java+
++Java+  
 
 ```java
 public final class HighScoreMutationPolicy implements StateMutationPolicy<Integer> {
@@ -40,7 +40,7 @@ public final class HighScoreMutationPolicy implements StateMutationPolicy<Intege
 ```
 
 +++  
-+Kotlin+
++Kotlin+  
 
 ```kotlin
 class HighScoreMutationPolicy : StateMutationPolicy<Int?> {
@@ -54,33 +54,33 @@ class HighScoreMutationPolicy : StateMutationPolicy<Int?> {
 ```
 
 +++  
--+-
+-+-  
 
 _The mutation policy in this example is not really needed; this is just an example of how it can be used._
 
 Now let's create a state with the new policy.
 
 -+-  
-+Java+
++Java+  
 
 ```java
 private final MutableState<Integer> highScoreState = MutableState.of(0, new HighScoreMutationPolicy());
 ```
 
 +++  
-+Kotlin+
++Kotlin+  
 
 ```kotlin
 private val highScoreState = mutableStateOf(0, HighScoreMutationPolicy())
 ```
 
 +++  
--+-
+-+-  
 
 Then we can change the GUI to support it.
 
 -+-  
-+Java+
++Java+  
 
 ```java
 final var gui = Gui.of(1)
@@ -127,7 +127,7 @@ gui.open(player);
 ```
 
 +++  
-+Kotlin+
++Kotlin+  
 
 ```kotlin
 val gui = buildGui {
@@ -183,7 +183,7 @@ gui.open(player)
 ```
 
 +++  
--+-
+-+-  
 
 When the GUI is opened for the first time the title will update with the clicks, once you close and re-open it, it'll
 only update once you reach a new high score.

triumph-gui/4_x_x/1-started/using-states.md

@@ -13,14 +13,14 @@ Kotlin examples require the `dev.triumphteam:triumph-gui-<platform>kotlin:<versi
 
 # Adding state
 
-A quick explanation of a (State)[/states] is that it's an object that can be "tied" to a (Component)[/components] which when 
+A quick explanation of a [State](/states) is that it's an object that can be "tied" to a [Component](/components) which when 
 modifier cause the component to re-render.  
 
 Let's take the previous example and add some a state to it. We can create a state that'll keep track of how many times 
 a `player` has clicked on the item.  
 
 -+-  
-+Java+
++Java+  
 
 ```java
 final var gui = Gui.of(1)
@@ -52,7 +52,7 @@ gui.open(player);
 ```
 
 +++  
-+Kotlin+
++Kotlin+  
 ```kotlin
 val gui = buildGui {
     // If not set, defaults to chest - 1 row
@@ -90,4 +90,4 @@ gui.open(player)
 +++  
 -+-  
 Congratulations you have built the most simple cookie clicker game!  
-But we can improve it even more, let's add title updating into the mix, read more in (here)[/updating-title].
+But we can improve it even more, let's add title updating into the mix, read more in [here](/updating-title).