Update docFX plugins and xrefs

docs/_template/description-generator/plugins/LICENSE

@@ -19,3 +19,11 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
+
+==============================================================================
+
+Humanizer (https://github.com/Humanizr/Humanizer)
+The MIT License (MIT)
+Copyright (c) .NET Foundation and Contributors
+
+==============================================================================

docs/_template/last-modified/plugins/LibGit2Sharp.dll.config

@@ -1,4 +1,4 @@
 <configuration>
-    <dllmap os="linux" cpu="x86-64" wordsize="64" dll="git2-ef5a385" target="lib/linux-x64/libgit2-ef5a385.so" />
-    <dllmap os="osx" cpu="x86,x86-64" dll="git2-ef5a385" target="lib/osx/libgit2-ef5a385.dylib" />
+    <dllmap os="linux" cpu="x86-64" wordsize="64" dll="git2-6777db8" target="lib/linux-x64/libgit2-6777db8.so" />
+    <dllmap os="osx" cpu="x86,x86-64" dll="git2-6777db8" target="lib/osx/libgit2-6777db8.dylib" />
 </configuration>

docs/_template/light-dark-theme/partials/head.tmpl.partial

@@ -10,7 +10,7 @@
   <meta property="og:locale" content="en-us">
   <meta property="og:type" content="website">
   <meta property="og:site_name" content="Discord.Net Docs">
-  <meta property="og:image" content="https://cdn.jsdelivr.net/gh/discord-net/Discord.Net/docs/marketing/logo/PackageLogo.png">
+  <meta property="og:image" content="https://raw.githubusercontent.com/Discord-Net-Labs/Discord.Net-Labs/release/3.x/docs/marketing/logo/PackageLogo.png">
   <meta property="og:image:alt" content="Discord.Net Logo">
   <meta name="theme-color" content="#995EA7"/>
   <meta name="generator" content="docfx {{_docfxVersion}}">

docs/docfx.json

@@ -10,7 +10,7 @@
       "dest": "api",
       "filter": "filterConfig.yml",
       "properties": {
-        "TargetFramework": "netstandard2.0"
+        "TargetFramework": "net5.0"
       }
     }
   ],
@@ -45,18 +45,6 @@
         ]
       }
     ],
-    "resource": [
-      {
-        "files": [
-          "**/images/**",
-          "**/samples/**",
-          "langwordMapping.yml",
-          "marketing/logo/**.svg",
-          "marketing/logo/**.png",
-          "favicon.ico"
-        ]
-      }
-    ],
     "dest": "_site",
     "template": [
       "default",

docs/guides/concepts/entities.md

@@ -31,8 +31,7 @@ But that doesn't mean a message _can't_ come from a
 retrieve information about a guild from a message entity, you will
 need to cast its channel object to a `SocketTextChannel`.
 
-You can find out various types of entities in the @FAQ.Misc.Glossary
-page.
+You can find out various types of entities in the [Glossary page.](xref:FAQ.Glossary)
 
 ## Navigation
 

docs/guides/getting_started/installing.md

@@ -11,7 +11,7 @@ may also compile this library yourself should you so desire.
 
 ## Supported Platforms
 
-Discord.Net targets [.NET 5.0], but is also available on older versions, like [.NET Standard] and [.NET Core]; this still means
+Discord.Net targets [.NET 6.0] and [.NET 5.0], but is also available on older versions, like [.NET Standard] and [.NET Core]; this still means
 that creating applications using the latest version of .NET (6.0)
 is most recommended. If you are bound by Windows-specific APIs or
 other limitations, you may also consider targeting [.NET Framework]
@@ -23,6 +23,7 @@ other limitations, you may also consider targeting [.NET Framework]
 > implementation and may crash the application upon startup.
 
 [Mono]: https://www.mono-project.com/
+[.NET 6.0]: https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-6
 [.NET 5.0]: https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-5
 [.NET Standard]: https://docs.microsoft.com/en-us/dotnet/articles/standard/library
 [.NET Core]: https://docs.microsoft.com/en-us/dotnet/articles/core/

docs/guides/int_framework/post-execution.md

@@ -16,7 +16,7 @@ If you are using the `RunMode.Async` to run your commands,
 you must use the Interaction Service events to get the execution results. When using `RunMode.Async`,
 [InteractionService.ExecuteCommandAsync] will always return a successful result.
 
-[InteractionService.ExecuteCommandAsync]: xref: Discord.Interactions.InteractionService.ExecuteCommandAsync*
+[InteractionService.ExecuteCommandAsync]: xref:Discord.Interactions.InteractionService.ExecuteCommandAsync*
 
 ## Results
 
@@ -39,7 +39,7 @@ Interaction Result come in a handful of different flavours:
 [ExecuteResult]: xref:Discord.Interactions.ExecuteResult
 [PreconditionGroupResult]: xref:Discord.Interactions.PreconditionGroupResult
 [PreconditionResult]: xref:Discord.Interactions.PreconditionResult
-[SearchResult]: xref:Discord.Interactions.SearchResult
+[SearchResult]: xref:Discord.Interactions.SearchResult`1
 [TypeConverterResult]: xref:Discord.Interactions.TypeConverterResult
 [IResult.Error]: xref:Discord.Interactions.IResult.Error*
 

docs/guides/text_commands/intro.md

@@ -187,7 +187,7 @@ service provider.
 
 ### Module Constructors
 
-Modules are constructed using @Guides.Commands.DI. Any parameters
+Modules are constructed using [Dependency Injection](xref:Guides.TextCommands.DI). Any parameters
 that are placed in the Module's constructor must be injected into an
 @System.IServiceProvider first.
 

docs/guides/v2_v3_guide/v2_to_v3_guide.md

@@ -27,4 +27,4 @@ There is a new event called `PresenceUpdated` that is called when a user's prese
 
 ## Migrating your commands to slash command
 
-The new InteractionService was designed to act like the previous service for text-based commands. Your pre-existing code will continue to work, but you will need to migrate your modules and response functions to use the new InteractionService methods. Docs on this can be found in the Guides section.
+The new InteractionService was designed to act like the previous service for text-based commands. Your pre-existing code will continue to work, but you will need to migrate your modules and response functions to use the new InteractionService methods. Docs on this can be found [here](xref:Guides.IntFw.Intro)

docs/index.md

@@ -79,10 +79,4 @@ Components of a message such as buttons and dropdowns, which can be interacted w
 Message components can be set in rows and multiple can exist on a single message!
 
 - Explanation on how to add & respond to message components can be found in the 
-[Message Component Guides](xref:Guides.MessageComponents.Intro)
-
-> [!Note]
-> More experienced users might want to refer to the
-> [API Documentation](xref:API.Docs) for a breakdown of the individual
-> components in the library.
-
+[Message Component Guides](xref:Guides.MessageComponents.Intro)