From 2f492859032c381789ca0c09285af54d39295765 Mon Sep 17 00:00:00 2001
From: Hsu Still <341464@gmail.com>
Date: Thu, 28 Sep 2017 11:28:05 +0800
Subject: [PATCH] Fix cross references in Logging

---
 docs/guides/concepts/logging.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/docs/guides/concepts/logging.md b/docs/guides/concepts/logging.md
index 1592dfc72..380c2786d 100644
--- a/docs/guides/concepts/logging.md
+++ b/docs/guides/concepts/logging.md
@@ -14,12 +14,14 @@ section.
 ### Usage
 
 To receive log events, simply hook the discord client's log method
-to a Task with a single parameter of type [LogMessage]
+to a `Task` with a single parameter of type [LogMessage].
 
 It is recommended that you use an established function instead of a
-lambda for handling logs, because most [addons] accept a reference
+lambda for handling logs, because most addons accept a reference
 to a logging function to write their own messages.
 
+[LogMessage]: xref:Discord.LogMessage
+
 ### Usage in Commands
 
 Discord.Net's [CommandService] also provides a log event, identical
@@ -29,6 +31,9 @@ Data logged through this event is typically coupled with a
 [CommandException], where information about the command's context
 and error can be found and handled.
 
+[CommandService]: Discord.Commands.CommandService
+[CommandException]: Discord.Commands.CommandException
+
 #### Samples
 
 [!code-csharp[Logging Sample](samples/logging.cs)]