Explain __mindex snippets a bit better

Author: Sainan

docs/New Features/Mindex Metamethod.md

@@ -1,15 +1,14 @@
 The `__mindex` metamethod stands for 'method index'. It has a secondary priority to `__index` and it's only invoked when the lookup is being performed by method invocation syntax. This is used to avoid compatibility issues regarding Pluto's default metatable for tables. For example:
 ```pluto
 local t = { "a", "b", "c" }
-print(t:concat())
+print(t:concat()) --> abc
 ```
 In this code, the following occurs:
 1. `concat` key is not directly present in the table, so `__index` is queried.
 2. `__index` returns nil.
 3. Since `__index` returned nil and this lookup is being performed by method invocation syntax (`:`), `__mindex` is queried.
 
-Another example:
-```pluto
+```pluto title="An example showing how __mindex is walked recursively so :insert still works with a custom __mindex"
 local t = setmetatable({}, {
     __mindex = {
         function sum()
@@ -27,8 +26,7 @@ print(t.sum) --> nil
 print(t:sum()) --> 3
 ```
 
-Beware of a caveat:
-```pluto
+```pluto title="An example of __index taking precedence"
 local t = { 1, 2 }
 print(t:min()) --> 1
 t.min = 1