Merge pull request #8795 from ntrel/ex-panels

[std/exception] Tweak docs

Signed-off-by: Nicholas Wilson <thewilsonator@users.noreply.github.com>
Merged-on-behalf-of: Nicholas Wilson <thewilsonator@users.noreply.github.com>

Author: dlang-bot

std/exception.d

@@ -416,13 +416,16 @@ void assertThrown(T : Throwable = Exception, E)
     Returns: `value`, if `cast(bool) value` is true. Otherwise,
     depending on the chosen overload, `new Exception(msg)`, `dg()` or `ex` is thrown.
 
-    Note:
-        `enforce` is used to throw exceptions and is therefore intended to
+        $(PANEL
+        $(NOTE `enforce` is used to throw exceptions and is therefore intended to
         aid in error handling. It is $(I not) intended for verifying the logic
-        of your program. That is what `assert` is for. Also, do not use
+        of your program - that is what `assert` is for.)
+
+        Do not use
         `enforce` inside of contracts (i.e. inside of `in` and `out`
         blocks and `invariant`s), because contracts are compiled out when
         compiling with $(I -release).
+        )
 
         If a delegate is passed, the safety and purity of this function are inferred
         from `Dg`'s safety and purity.
@@ -836,7 +839,7 @@ string letters()
 )
 
 The use in the example above is correct because `result`
-was private to `letters` and is inaccessible in writing
+was private to `letters` and the memory it referenced can no longer be written to
 after the function returns. The following example shows an
 incorrect use of `assumeUnique`.
 
@@ -859,22 +862,23 @@ string letters(char first, char last)
 ----
 )
 
-The example above wreaks havoc on client code because it is
-modifying arrays that callers considered immutable. To obtain an
+The example above wreaks havoc on client code because it modifies the
+returned array that the previous caller considered immutable. To obtain an
 immutable array from the writable array `buffer`, replace
 the last line with:
 
 ----
 return to!(string)(sneaky); // not that sneaky anymore
 ----
 
-The call will duplicate the array appropriately.
+The `to` call will duplicate the array appropriately.
 
-Note that checking for uniqueness during compilation is
+$(PANEL
+$(NOTE Checking for uniqueness during compilation is
 possible in certain cases, especially when a function is
-marked as a pure function. The following example does not
+marked (or inferred) as `pure`. The following example does not
 need to call `assumeUnique` because the compiler can infer the
-uniqueness of the array in the pure function:
+uniqueness of the array in the pure function:)
 
 $(RUNNABLE_EXAMPLE
 ----
@@ -894,6 +898,7 @@ For more on infering uniqueness see the $(B unique) and
 $(B lent) keywords in the
 $(HTTP www.cs.cmu.edu/~aldrich/papers/aldrich-dissertation.pdf, ArchJava)
 language.
+)
 
 The downside of using `assumeUnique`'s
 convention-based usage is that at this time there is no