Fix links

Author: mythz

MyApp/_pages/advantages-of-message-based-web-services.md

@@ -126,11 +126,11 @@ Since it promotes clean, re-usable code, ServiceStack has always encouraged the
 
   - In Request and Response DTO's (on client and server) 
   - In [JSON, JSV and CSV Text Serializers](/formats)
-  - As the data model in [OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite), [db4o](http://code.google.com/p/servicestack/source/browse/#svn%2Ftrunk%2FCommon%2FServiceStack.DataAccess%2FServiceStack.DataAccess.Db4oProvider) and [NHibernate](http://code.google.com/p/servicestack/source/browse/#svn%2Ftrunk%2FCommon%2FServiceStack.DataAccess%2FServiceStack.DataAccess.NHibernateProvider%253Fstate%253Dclosed)
-  - As the entities stored in [Redis](https://github.com/ServiceStack/ServiceStack.Redis)
+  - As the data model in [OrmLite](/ormlite/), [db4o](http://code.google.com/p/servicestack/source/browse/#svn%2Ftrunk%2FCommon%2FServiceStack.DataAccess%2FServiceStack.DataAccess.Db4oProvider) and [NHibernate](http://code.google.com/p/servicestack/source/browse/#svn%2Ftrunk%2FCommon%2FServiceStack.DataAccess%2FServiceStack.DataAccess.NHibernateProvider%253Fstate%253Dclosed)
+  - As the entities stored in [Redis](/redis/)
   - As blobs stored in [Caches](/caching) and [Sessions](/auth/sessions)
   - Dropped and executed in [MQ's services](/redis-mq)
-  - Dehydrating [complex configurations](http://www.servicestack.net/mvc-powerpack/) into
+  - Dehydrating complex configurations into
 
 Leveraging different technologies whose functionality is built around POCO's offer un-precedented levels of re-use, reduces friction, promotes consistent, more usable and easier to rationale code-bases.
 

MyApp/_pages/api-design.md

@@ -50,7 +50,7 @@ Which your C# clients will still be able to call with:
 List<Contact> response = client.Get(new GetContacts());
 ```
 
-This will make a **GET** call to the custom `/contacts` URL and returns all rows from the `Contact` Table in the configured RDBMS using [OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite)
+This will make a **GET** call to the custom `/contacts` URL and returns all rows from the `Contact` Table in the configured RDBMS using [OrmLite](/ormlite/)
 `Select()` extension method on the `base.Db` ADO.NET `IDbConnection` property on ServiceStack's convenience `Service` base class. 
 
 Using `Get()` limits access to this service from HTTP **GET** requests only, all other HTTP Verbs requests to `/contacts` will return a **404 NotFound** HTTP Error Response.
@@ -309,7 +309,7 @@ IncludeTypes: WebApi.*,WebAndMobileApi.*
 
 ### Micro ORMs and ADO.NET's IDbConnection
 
-Code-First Micro ORMS like [OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite) and 
+Code-First Micro ORMS like [OrmLite](/ormlite/) and 
 [Dapper](https://github.com/StackExchange/Dapper) provides a pleasant high-level experience whilst working directly against ADO.NET's low-level `IDbConnection`. They both support all major databases so you immediately have access to a flexible RDBMS option out-of-the-box. At the same time you're not limited to using the providers contained in the `Service` class and can continue to use your own register IOC dependencies (inc. an alternate IOC itself). 
 
 ### Micro ORM POCOs make good DTOs

MyApp/_pages/appsettings.md

@@ -87,7 +87,7 @@ AppSettings = new MultiAppSettingsBuilder()
 
 ## OrmLite AppSettings
 
-`OrmLiteAppSettings` provides an alternative read/write API that lets you maintain your applications configuration in any [RDBMS back-end OrmLite supports](https://github.com/ServiceStack/ServiceStack.OrmLite/#download). It works like a mini Key/Value database in which can store any serializable value against any key which is maintained into the simple Id/Value `ConfigSettings` table.
+`OrmLiteAppSettings` provides an alternative read/write API that lets you maintain your applications configuration in any [RDBMS back-end OrmLite supports](/ormlite/). It works like a mini Key/Value database in which can store any serializable value against any key which is maintained into the simple Id/Value `ConfigSettings` table.
 
 ### Usage
 

MyApp/_pages/auth/auth-repository.md

@@ -309,7 +309,7 @@ If you need finer-grained access than the shared APIs above, you can update the
 in your preferred persistence provider directly.
 
 E.g. if you're using the `OrmLiteAuthRepository` to store your Users in an RDBMS back-end you can use 
-[OrmLite APIs](https://github.com/ServiceStack/ServiceStack.OrmLite) to update the user details stored in the `UserAuth` and `UserAuthDetails`
+[OrmLite APIs](/ormlite/) to update the user details stored in the `UserAuth` and `UserAuthDetails`
 tables, e.g:
 
 ```csharp

MyApp/_pages/auto-batched-requests.md

@@ -89,7 +89,7 @@ public class MyServices : Service
 
 So with this custom implementation we've gone from **100 HTTP Requests + 100 Redis Operations** to **1 HTTP Request + 1 Redis Operation**.
 
-Another scenario where you may consider using a **Custom Batched Implementation** is if you wanted to execute all requests within a single RDBMS transaction, which with [OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite) would look something like:
+Another scenario where you may consider using a **Custom Batched Implementation** is if you wanted to execute all requests within a single RDBMS transaction, which with [OrmLite](/ormlite/) would look something like:
 
 ```csharp
 public class MyServices : Service

MyApp/_pages/autoquery/autogen.md

@@ -261,7 +261,7 @@ public class ConfigureDb : IHostingStartup
 ```
 
 The [sqlite](https://gist.github.com/gistlyn/768d7b330b8c977f43310b954ceea668) gist registers an
-[OrmLite.Sqlite](https://github.com/ServiceStack/ServiceStack.OrmLite) RDBMS connection with our App which we want to configure to connect to a **northwind.sqlite** database:
+[OrmLite.Sqlite](/ormlite/) RDBMS connection with our App which we want to configure to connect to a **northwind.sqlite** database:
 
 ```csharp
 public void Configure(IServiceCollection services)

MyApp/_pages/autoquery/dynamodb.md

@@ -85,7 +85,7 @@ or `DynamoDbSource` and the only thing that would need to change to have it quer
 `QueryDb<T>` base class.
 
 The text in comments highlight that when the `RockstarAlbum` POCO is stored in an RDBMS 
-[OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite) 
+[OrmLite](/ormlite/) 
 creates the table with the `Id` as the Primary Key and `RockstarId` as a Foreign Key to the `Rockstar` table. 
 This is different in DynamoDB where 
 [PocoDynamo](/aws-pocodynamo) behavior is to keep related records together so

MyApp/_pages/autoquery/rdbms.md

@@ -2,7 +2,7 @@
 title: AutoQuery RDBMS
 ---
 
-AutoQuery RDBMS enables the rapid development of high-performance, fully-queryable typed RDBMS data-driven services with just a POCO Request DTO class definition and [supports most major RDBMS](/ormlite/#ormlite-rdbms-providers) courtesy of building on [OrmLite's high-performance RDBMS-agnostic API's](https://github.com/ServiceStack/ServiceStack.OrmLite).
+AutoQuery RDBMS enables the rapid development of high-performance, fully-queryable typed RDBMS data-driven services with just a POCO Request DTO class definition and [supports most major RDBMS](/ormlite/#ormlite-rdbms-providers).
 
 ### AutoQuery Services are ServiceStack Services
 
@@ -30,7 +30,7 @@ If you don't have OrmLite configured it can be registered with a 1-liner by spec
 services.AddOrmLite(options => options.UseSqlite(connString));
 ```
 
-The above config registers an In Memory Sqlite database although as the AutoQuery test suite works in all [supported RDBMS providers](https://github.com/ServiceStack/ServiceStack.OrmLite/#download) you're free to use your registered DB of choice.
+The above config registers an In Memory Sqlite database although as the AutoQuery test suite works in all [supported RDBMS providers](/ormlite/) you're free to use your registered DB of choice.
 
 The `MaxLimit` option ensures each query returns a maximum limit of **100** rows.
 
@@ -145,7 +145,7 @@ Dictionary<string,string> queryArgs = Request.GetRequestParams();
 var q = AutoQuery.CreateQuery(dto, queryArgs, Request, db);
 ```
 
-Which constructs an [OrmLite SqlExpression](https://github.com/ServiceStack/ServiceStack.OrmLite/#examples) 
+Which constructs an [OrmLite SqlExpression](/ormlite/) 
 from typed properties on the Request DTO as well as any untyped key/value pairs on the HTTP Requests 
 **QueryString** or **FormData**.
 
@@ -202,7 +202,7 @@ In the example above we're returning only a subset of results. Unmatched propert
 
 ## Returning Nested Related Results
 
-AutoQuery also takes advantage of [OrmLite's References Support](https://github.com/ServiceStack/ServiceStack.OrmLite/#reference-support-poco-style) which lets you return related child records that are annotated with `[Reference]` attribute, e.g:
+AutoQuery also takes advantage of [OrmLite's References Support](/ormlite/reference-support) which lets you return related child records that are annotated with `[Reference]` attribute, e.g:
 
 ```csharp
 public class QueryRockstars : QueryDb<Rockstar> {}
@@ -221,7 +221,7 @@ public class Rockstar
 
 ## Joining Tables
 
-AutoQuery lets us take advantage of OrmLite's recent [support for JOINs in typed SqlExpressions](https://github.com/ServiceStack/ServiceStack.OrmLite/#typed-sqlexpression-support-for-joins) 
+AutoQuery lets us take advantage of OrmLite's recent [support for JOINs in typed SqlExpressions](/ormlite/typed-joins) 
 
 We can tell AutoQuery to join on multiple tables using the `IJoin<T1,T2>` interface marker:
 
@@ -234,9 +234,9 @@ public class QueryRockstarAlbums
 }
 ```
 
-The above example tells AutoQuery to query against an **INNER JOIN** of the `Rockstar` and `RockstarAlbum` tables using [OrmLite's reference conventions](https://github.com/ServiceStack/ServiceStack.OrmLite/#reference-conventionst) that's implicit between both tables.
+The above example tells AutoQuery to query against an **INNER JOIN** of the `Rockstar` and `RockstarAlbum` tables using [OrmLite's reference conventions](/ormlite/reference-support) that's implicit between both tables.
 
-The Request DTO lets us query against fields across the joined tables where each field is matched with the [first table containing the field](https://github.com/ServiceStack/ServiceStack.OrmLite/#selecting-multiple-columns-across-joined-tables). You can match against fields using the fully qualified `{Table}{Field}` convention, e.g. `RockstarAlbumName` queries against the `RockstarAlbum`.`Name` column.
+The Request DTO lets us query against fields across the joined tables where each field is matched with the [first table containing the field](/ormlite/dynamic-result-sets). You can match against fields using the fully qualified `{Table}{Field}` convention, e.g. `RockstarAlbumName` queries against the `RockstarAlbum`.`Name` column.
 
 This mapping of fields also applies to the Response DTO where now `RockstarAlbumName` from the above `CustomRockstar` type will be populated:
 
@@ -670,7 +670,7 @@ services.AddPlugin(new AutoQueryFeature { EnableUntypedQueries = false });
 
 It's also possible to specify Raw SQL Filters. Whilst offering greater flexibility they also suffer from many of the problems that OData's expressions have. 
 
-Raw SQL Filters also don't benefit from limiting matching to declared fields and auto-escaping and quoting of values although they're still validated against OrmLite's [IllegalSqlFragmentTokens](https://github.com/ServiceStack/ServiceStack.OrmLite/blob/master/src/ServiceStack.OrmLite/OrmLiteUtilExtensions.cs#L172) to protect against SQL Injection attacks. But as they still allow calling SQL Functions, Raw SqlFilters shouldn't be enabled when accessible by untrusted parties unless they've been configured to use a [Named OrmLite DB Connection](https://github.com/ServiceStack/ServiceStack.OrmLite/#multi-nested-database-connections) which is read-only and locked-down so that it only has access to what it's allowed to.
+Raw SQL Filters also don't benefit from limiting matching to declared fields and auto-escaping and quoting of values although they're still validated against OrmLite's [IllegalSqlFragmentTokens](https://github.com/ServiceStack/ServiceStack/blob/d0b6acf38cc45c16d229df66b82183644e0aee3c/ServiceStack.OrmLite/src/ServiceStack.OrmLite/OrmLiteUtils.cs#L501) to protect against SQL Injection attacks. But as they still allow calling SQL Functions, Raw SqlFilters shouldn't be enabled when accessible by untrusted parties unless they've been configured to use a [Named OrmLite DB Connection](/ormlite/multi-database-connections) which is read-only and locked-down so that it only has access to what it's allowed to.
 
 If safe to do so, RawSqlFilters can be enabled with:
 

MyApp/_pages/aws-pocodynamo.md

@@ -10,7 +10,7 @@ NoSQL [DynamoDB](https://aws.amazon.com/dynamodb/).
 ## First class support for reusable, code-first POCOs
 
 PocoDynamo is conceptually similar to ServiceStack's other code-first
-[OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite) and 
+[OrmLite](/ormlite/) and 
 [Redis](https://github.com/ServiceStack/ServiceStack.Redis) clients by providing a high-fidelity, managed client that enhances
 AWSSDK's low-level [IAmazonDynamoDB client](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/UsingAWSsdkForDotNet.html), 
 with rich, native support for intuitively mapping your re-usable code-first POCO Data models into 

MyApp/_pages/aws.md

@@ -463,7 +463,7 @@ NoSQL [DynamoDB](https://aws.amazon.com/dynamodb/).
 #### First class support for reusable, code-first POCOs
 
 It works conceptually similar to ServiceStack's other code-first
-[OrmLite](https://github.com/ServiceStack/ServiceStack.OrmLite) and 
+[OrmLite](/ormlite/) and 
 [Redis](https://github.com/ServiceStack/ServiceStack.Redis) clients by providing a high-fidelity, managed client that enhances
 AWSSDK's low-level [IAmazonDynamoDB client](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/UsingAWSsdkForDotNet.html), 
 with rich, native support for intuitively mapping your re-usable code-first POCO Data models into