Fixed docs and wiki links & spelling

Author: niemyjski

.vscode/settings.json

@@ -13,13 +13,20 @@
         "Reindex",
         "Reindexing",
         "Serilog",
+        "Trello",
         "Varorbc",
         "Zurb",
         "Zurb's",
+        "adamsitnik",
+        "caesay",
         "deduplicated",
         "edwardmeng",
+        "eleventy",
         "exceptionless",
+        "frankebersoll",
+        "pluggable",
         "serializers",
+        "srijken",
         "typeof",
         "walkthrough"
     ]

content/docs/clients/dotnet/configuration.md

@@ -82,7 +82,7 @@ Exceptionless can be configured using a config section in your web.config or app
 
 ## Versioning
 
-By specifying an application version you can [enable additional functionality](https://github.com/exceptionless/Exceptionless/wiki/Versioning). By default, an application version will try to be resolved from assembly attributes.  However, it's a good practice to specify an application version if possible using the code below.
+By specifying an application version you can [enable additional functionality](/docs/versioning/). By default, an application version will try to be resolved from assembly attributes.  However, it's a good practice to specify an application version if possible using the code below.
 
 ```csharp
 using Exceptionless;
@@ -130,7 +130,7 @@ using Exceptionless.Configuration;
 
 ## Self Hosted Options
 
-The Exceptionless client can also be configured to send data to your self hosted instance. This is configured by setting the `serverUrl` setting to point to your Exceptionless instance. 
+The Exceptionless client can also be configured to send data to your self hosted instance. This is configured by setting the `serverUrl` setting to point to your Exceptionless instance.
 
 ### Configuration file
 

content/docs/clients/dotnet/private-information.md

@@ -19,7 +19,7 @@ You have the option of finely tuning what is collected via individual setting op
 ExceptionlessClient.Default.Configuration.IncludePrivateInformation = false;
 ```
 
-If you wish to have a finer grained approach which allows you to use Data Exclusions while removing specific meta data collection you can do so via code. Please note if the below doesn't meet your needs you can always [write a plugin](https://github.com/exceptionless/Exceptionless.Net/wiki/Adding-Plugins).
+If you wish to have a finer grained approach which allows you to use Data Exclusions while removing specific meta data collection you can do so via code. Please note if the below doesn't meet your needs you can always [write a plugin](/docs/clients/dotnet/plugins/).
 
 ## Configuration
 

content/docs/clients/dotnet/sending-events.md

@@ -132,7 +132,7 @@ private void OnSubmittingEvent(object sender, EventSubmittingEventArgs e) {
 
 Using major logging frameworks like NLog or Log4net gives you more granular control over what's logged.
 
-To use the [NLog](https://www.nuget.org/packages/exceptionless.nlog) or [Log4net](https://www.nuget.org/packages/exceptionless.log4net) clients, bring down the nuget package and follow the detailed readme. You can also take a look at our [sample app](https://github.com/exceptionless/Exceptionless.Net/tree/master/samples/Exceptionless.SampleConsole), which uses both frameworks.
+To use the [NLog](https://www.nuget.org/packages/exceptionless.nlog) or [Log4net](https://www.nuget.org/packages/exceptionless.log4net) clients, bring down the NuGet package and follow the detailed readme. You can also take a look at our [sample app](https://github.com/exceptionless/Exceptionless.Net/tree/master/samples/Exceptionless.SampleConsole), which uses both frameworks.
 
 **Performance Note**
 If you are logging thousands of messages a minute, you should use the in-memory event storage (below). This way, the client won't serialize the log events to disk, thus is much faster. This does mean, however, that if the application dies you will lose unsent events in memory. When you use the NLog or Log4net targets and specify the API key as part of the target configuration, we will automatically create a second client instance that uses in-memory storage only for log messages. This way, any logged exceptions or feature usages still use disk storage, while log messages use in-memory storage, allowing maximum performance.
@@ -142,6 +142,6 @@ using Exceptionless;
 ExceptionlessClient.Default.Configuration.UseInMemoryStorage();
 ```
 
----  
+---
 
 [Next > Supported Platforms](supported-platforms) {.text-right}

content/docs/clients/javascript/client-configuration-values.md

@@ -8,7 +8,8 @@ order: 2
 - [Subscribing to Client Configuration Setting changes](#subscribing-to-client-configuration-setting-changes)
 
 ## About
-[Read about client configuration and view in-depth examples](https://github.com/exceptionless/Exceptionless/wiki/Project-Settings#client-configuration)
+
+[Read about client configuration and view in-depth examples](/docs/project-settings/#client-configuration)
 
 ## Usage Example
 
@@ -23,13 +24,13 @@ Then, we register a new client side plugin that runs each time an event is creat
 ```javascript
 exceptionless.ExceptionlessClient.default.config.addPlugin('Conditionally cancel log submission', 100, function (context, next) {
     var enableLogSubmission = context.client.config.settings['enableLogSubmission'];
- 
+
     // only cancel event submission if it’s a log event and
     // enableLogSubmission is set to a value and the value is not true.
     if (context.event.type === 'log' && (!!enableLogSubmission && enableLogSubmission !== 'true')) {
        context.cancelled = true;
     }
- 
+
     next();
 });
 ```
@@ -41,11 +42,11 @@ exceptionless.ExceptionlessClient.default.config.addPlugin('Conditionally cancel
 
 ![Exceptionless Client Configuration Settings](../../../assets/img/docs/client-configuration.png)
 
-All project settings are synced to the client in almost real time. When an event is submitted to Exceptionless we send down a response header with the current configuration version. If a newer version is available we will immediately retrieve and apply the latest configuration. 
+All project settings are synced to the client in almost real time. When an event is submitted to Exceptionless we send down a response header with the current configuration version. If a newer version is available we will immediately retrieve and apply the latest configuration.
 
-By default the client will check after `5 seconds` on client startup (*if no events are submitted on startup*) and then every `2 minutes` after the last event submission for updated configuration settings. 
-  * Checking for updated settings doesn't count towards plan limits. 
-  * Only the current configuration version is sent when checking for updated settings (no user information will ever be sent). 
+By default the client will check after `5 seconds` on client startup (*if no events are submitted on startup*) and then every `2 minutes` after the last event submission for updated configuration settings.
+  * Checking for updated settings doesn't count towards plan limits.
+  * Only the current configuration version is sent when checking for updated settings (no user information will ever be sent).
   * If the settings haven't changed, then no settings will be retrieved.
 
 You can also **turn off the automatic updating of configuration settings when idle** using the code below.
@@ -67,6 +68,6 @@ exceptionless.SettingsManager.onChanged(function(configuration) {
 });
 ```
 
----  
+---
 
 [Next > Sending Events](sending-events) {.text-right}

content/docs/clients/javascript/client-configuration.md

@@ -28,7 +28,7 @@ order: 1
 
 ### Node.js
 
-1. Install the package by running `npm install exceptionless --save-dev`. 
+1. Install the package by running `npm install exceptionless --save-dev`.
 1. Add the Exceptionless client to your app:
 
 ```javascript
@@ -94,25 +94,29 @@ submissionBatchSize: 100
 });
 ```
 
-**NOTE**: creating new instances is good for sending custom events. **Automatic catching of errors uses default client**. Make sure you setup default client as well if you need automatic catching of unhandled errors. 
+**NOTE**: creating new instances is good for sending custom events. **Automatic catching of errors uses default client**. Make sure you setup default client as well if you need automatic catching of unhandled errors.
 
 
 ### General Data Protection Regulation
-By default the Exceptionless Client will report all available metadata which could include potential PII data. There are various ways to limit the scope of PII data collection. For example, one could use [Data Exclusions](https://github.com/exceptionless/Exceptionless/wiki/Security#data-exclusions) to remove sensitive values but it only applies to specific collection points such as `Cookie Keys`, `Form Data Keys`, `Query String Keys` and `Extra Exception properties`. Additional data may need to be removed for the GDPR like the collection of user names and IP Addresses. Shown below is several examples of how you can configure the client to remove this additional metadata.
+
+By default the Exceptionless Client will report all available metadata which could include potential PII data. There are various ways to limit the scope of PII data collection. For example, one could use [Data Exclusions](/docs/security/#data-exclusions) to remove sensitive values but it only applies to specific collection points such as `Cookie Keys`, `Form Data Keys`, `Query String Keys` and `Extra Exception properties`. Additional data may need to be removed for the GDPR like the collection of user names and IP Addresses. Shown below is several examples of how you can configure the client to remove this additional metadata.
 
 You have the option of finely tuning what is collected via individual setting options or you can disable the collection of all PII data by setting the `includePrivateInformation` to `false`.
 
 #### Query String
+
 ```javascript
 <script src="bower_components/exceptionless/dist/exceptionless.min.js?apiKey=API_KEY_HERE& includePrivateInformation=false"></script>
 ```
 
 #### JavaScript
+
 ```javascript
 exceptionless.ExceptionlessClient.default.config.includePrivateInformation = false;
 ```
 
 #### Node.js
+
 ```javascript
 var exceptionless = require('exceptionless');
 exceptionless.ExceptionlessClient.default.config.includePrivateInformation = false;
@@ -121,6 +125,7 @@ exceptionless.ExceptionlessClient.default.config.includePrivateInformation = fal
 If you wish to have a finer grained approach which allows you to use Data Exclusions while removing specific meta data collection you can do so via code. Please note if the below doesn't meet your needs you can always write a plugin.
 
 #### JavaScript
+
 ```javascript
 // Include the username if available.
 exceptionless.ExceptionlessClient.default.config.includeUserName = false;
@@ -137,6 +142,7 @@ exceptionless.ExceptionlessClient.default.config.includeQueryString = false;
 ```
 
 #### Node.js
+
 ```javascript
 var exceptionless = require('exceptionless');
 
@@ -155,14 +161,17 @@ exceptionless.ExceptionlessClient.default.config.includeQueryString = false;
 ```
 
 ## Versioning
-By specifying an application version you can [enable additional functionality](https://github.com/exceptionless/Exceptionless/wiki/Versioning). It's a good practice to specify an application version if possible using the code below.
+
+By specifying an application version you can [enable additional functionality](/docs/versioning/). It's a good practice to specify an application version if possible using the code below.
 
 ### JavaScript
+
 ```javascript
 exceptionless.ExceptionlessClient.default.config.setVersion("1.2.3");
 ```
 
 ### Node.js
+
 ```javascript
 var exceptionless = require('exceptionless');
 exceptionless.ExceptionlessClient.default.config.setVersion("1.2.3");
@@ -188,6 +197,7 @@ You can set the `serverUrl` on the default ExceptionlessClient instance.
 var client = require('exceptionless.node').ExceptionlessClient.default;
 client
 ```
---- 
+
+---
 
 [Next > Client Configuration Values](client-configuration-values) {.text-right}

content/docs/notifications.md

@@ -5,10 +5,10 @@ order: 11
 
 To turn on email notifications, go to "My Account" in your dashboard, then click on the "Notifications" tab.
 
-Once your'e in there, you can select the project you want to edit notifications to, and then select which notifications you want to receive for that selected project.
+Once you're in there, you can select the project you want to edit notifications to, and then select which notifications you want to receive for that selected project.
 
 ![Email Notifications](img/email-notification-settings.png)
 
 ---
 
-[Next > Log Levels](setting-log-levels) {.text-right}
+[Next > Log Levels](setting-log-levels) {.text-right}

content/docs/self-hosting/upgrading-self-hosted-instance.md

@@ -29,9 +29,9 @@ Version 6 added support for Elasticsearch 7, which requires a complete data migr
 
 ## Upgrading from v4 to v5
 
-We now only provide official docker images as release artifacts. This tutorial assumes you have docker/Kubernetes installed and have followed the [setup guide](https://github.com/exceptionless/Exceptionless/wiki/Self-Hosting).
+We now only provide official docker images as release artifacts. This tutorial assumes you have docker/Kubernetes installed and have followed the [setup guide](/docs/self-hosting/).
 
-1. We now can run on linux or windows as we are running on ASP.NET Core! As a result we've completely redone the configuration. For the most part we've prefixed configuration with `EX_` and simplified it as much as possible. I'd recommend taking a look at your previous configuration settings and then read over the following [configuration document](https://github.com/exceptionless/Exceptionless/wiki/Self-Hosting#configuration) to migrate your settings.
+1. We now can run on linux or windows as we are running on ASP.NET Core! As a result we've completely redone the configuration. For the most part we've prefixed configuration with `EX_` and simplified it as much as possible. I'd recommend taking a look at your previous configuration settings and then read over the following [configuration document](/docs/self-hosting/kubernetes/#configuration) to migrate your settings.
 2. Please note that no Elasticsearch changes are required. You can continue to use your existing Elasticsearch cluster. You just need to update the connection string by following step 1.
 3. Please note that the UI and API no longer run on the same port as they are now two different docker images. You may need to update your server url accordingly in your client applications.
 

content/news/2013/2013-12-19-exceptionless-1-2-0-released.md

@@ -23,6 +23,6 @@ Update your NuGet packages to take advantage of these improvements!
 * AddObject now serializes objects to a depth of 5 by default.
 * Fixed a couple bugs that may occur when multiple client instances are running on the same machine concurrently.
 * Fixed a bug with the ExceptionlessWcfHandleErrorAttribute where it wouldn't catch errors when aspNetCompatibilityEnabled was set to false.
-* The client now submits errors to [collector.exceptionless.com/api/v1/error](http://collector.exceptionless.com/api/v1/error).
+* The client now submits errors to [collector.exceptionless.com/api/v1/error](https://collector.exceptionless.com/api/v1/error).
 * Fixed a bug that would prevent the Windows Form client from showing the Crash Report dialog.
 * Fixed a bug where multiple HttpModule sections could be added by the NuGet installer.

content/news/2014/2014-02-07-xml-parsing-exception-caught-fixed-case-study.md

@@ -30,12 +30,10 @@ Along with the sheer number of occurrences, it was also noticeably slowing the s
 
 The fix was relatively simple. The client now checks for "$" in cookie names within the affected method and just doesn't handle them.
 
-**Tracking errors like this is what we're all about.** There are hundreds of thousands, probably even millions, of bugs out there _right now _that throw exceptions every day but manage to remain hidden in the shadows of code written by professional developers.
+**Tracking errors like this is what we're all about.** There are hundreds of thousands, probably even millions, of bugs out there _right now_ that throw exceptions every day but manage to remain hidden in the shadows of code written by professional developers.
 
 It's not a sign of poor programming, it simply comes with the territory. You will have bugs, big and small, in every project you work on. The difference is, with Exceptionless, you can actually be aware of, and fix, them!
 
-Another bug bites the dust, thanks to help of Exceptionless' [real-time exception reporting](http://exceptionless.com "Real Time Exception Reporting")!
+Another bug bites the dust, thanks to help of Exceptionless' [real-time exception reporting](https://exceptionless.com "Real Time Exception Reporting")!
 
 Do you have a story where our software helped you track down and squash an elusive error? Let us know! We'll publish the details and link back to your app, if you like.
-
-

content/news/2014/2014-02-13-exceptionless-1-3-released.md

@@ -55,7 +55,7 @@ Exceptionless 1.3 brings with it both server and client changes, including [open
       Adding binding redirects to the right version.
     </li>
     <li>
-      Data Exclusions now <a href="http://docs.exceptionless.com/contents/security/" target="_blank">support wildcards</a>.
+      Data Exclusions now <a href="/docs/security/" target="_blank">support wildcards</a>.
     </li>
   </ul>
 </div>

content/news/2014/2014-05-20-exceptionless-2-in-the-making.md

@@ -12,15 +12,15 @@ Exceptionless 2.0 will include many of the feature requests that have come in si
 
 Many users have asked for ways to use Exceptionless to report additional types of events, rather than just errors. With 2.0, we are moving to an event based system that will accommodate this.
 
-## <a href="https://github.com/exceptionless/Exceptionless/wiki/Exceptionless-2.0-Overview#api-simplified" name="user-content-api-simplified"></a>API Simplified
+## <a href="/news/2014/2014-06-12-upcoming-exceptionless-2-0-simplified-api/#api-simplified" name="user-content-api-simplified">API Simplified</a>
 
 Since [going open source](/fork-us-exceptionless-goes-open-source/ "Fork Us! Exceptionless Goes Open Source"), we've wanted to simplify the API and make it easier to work with. We're taking the time to do it now, and it's going to be **awesome.** Watch out!
 
-## <a href="https://github.com/exceptionless/Exceptionless/wiki/Exceptionless-2.0-Overview#pluggable-system" name="user-content-pluggable-system"></a>Pluggable System
+## <a href="/news/2014/2014-06-25-coming-exceptionless-2-0-pluggable-system/" name="user-content-pluggable-system">Pluggable System</a>
 
 Plugins will allow customization and translation throughout the Exceptionless platform, including integration with third-party services and more.
 
-### <span style="color: inherit; font-family: inherit; font-size: 31.5px;">Client Rewrite</span>
+## Client Rewrite
 
 The client is being re-written be highly simplified and extensible, opening up platform support and ease of functionality additions.
 

content/news/2014/2014-06-12-upcoming-exceptionless-2-0-simplified-api.md

@@ -14,9 +14,9 @@ Exceptionless 2.0, [coming soon](/exceptionless-2-in-the-making/ "Exceptionless
 
 * <a href="https://api.exceptionless.io/docs/index.html" target="_blank">New REST API documentation and samples site.<br /> </a>Take a look and let us know what you think![![Exceptionless API Documentation](/assets/img/news/Screen-shot-2014-06-11-at-5.20.44-PM-300x225.png)](/assets/Screen-shot-2014-06-11-at-5.20.44-PM.png)<a style="color: #4183c4;" href="https://api.exceptionless.io/docs/index.html"><br /> </a>
 * Event POSTs take the raw data and use a plugin system to interpret that data and translate them into events.
-    * This allows us to take literally any data and turn it into events in the system.
-    * The POST data is captured as a raw bytes and added immediately added to a queue for processing.
-    * Plugins can easily be created to support new data formats like system logs.
+  * This allows us to take literally any data and turn it into events in the system.
+  * The POST data is captured as a raw bytes and added immediately added to a queue for processing.
+  * Plugins can easily be created to support new data formats like system logs.
 * This simplified API will make creating libraries for other platforms dead simple.
 * The API lives in a separate project and can be hosted on high-performance systems like the new Helios IIS host.
 * Makes it easy for us to migrate the UI to a SPA app.