fixing the docs internal links on GitHub

Author: maximv

docs/DryIoc.Docs/CreatingAndDisposingContainer.cs

@@ -43,7 +43,7 @@ [Test] public void Example()
 ```
 
 As you see, it is possible to additionally specify the `rules` and 
-the [`scopeContext`](ReuseAndScopes#what-scopecontext-is).
+the [`scopeContext`](ReuseAndScopes.md#what-scopecontext-is).
 
 
 ### Rules
@@ -83,7 +83,7 @@ public void Example()
 ### ScopeContext
 
 ScopeContext is an __optional__ ambient context for the new open scopes to be bound to. 
-It is described in details [here](ReuseAndScopes#scopecontext).
+It is described in details [here](ReuseAndScopes.md#scopecontext).
 
 
 ## Disposing Container

docs/DryIoc.Docs/CreatingAndDisposingContainer.md

@@ -42,7 +42,7 @@ class Creating_container_with_explicit_defaults
 ```
 
 As you see, it is possible to additionally specify the `rules` and 
-the [`scopeContext`](ReuseAndScopes#what-scopecontext-is).
+the [`scopeContext`](ReuseAndScopes.md#what-scopecontext-is).
 
 
 ### Rules
@@ -82,7 +82,7 @@ class Adding_some_rules_with_action
 ### ScopeContext
 
 ScopeContext is an __optional__ ambient context for the new open scopes to be bound to. 
-It is described in details [here](ReuseAndScopes#scopecontext).
+It is described in details [here](ReuseAndScopes.md#scopecontext).
 
 
 ## Disposing Container

docs/DryIoc.Docs/Decorators.cs

@@ -23,7 +23,7 @@
     - [Reusing the scoped service from the parent scope](#reusing-the-scoped-service-from-the-parent-scope)
 
 
-[FactoryMethod]:SelectConstructorOrFactoryMethod#factory-method-instead-of-constructor
+[FactoryMethod]:SelectConstructorOrFactoryMethod.md#factory-method-instead-of-constructor
 
 ## Overview
 
@@ -536,7 +536,7 @@ public void Example()
 
 DryIoc supports decorating of wrappers directly to adjust corresponding wrapper behavior, to add new functionality, to apply filtering, etc.
 
-Consider the decorating of [collection wrapper](Wrappers#ienumerable-or-array-of-a).
+Consider the decorating of [collection wrapper](Wrappers.md#ienumerable-or-array-of-a).
 Let`s say we want to change the default collection behavior and exclude keyed services from the result:
 
 ```cs md*/
@@ -647,7 +647,7 @@ which is a decorator in disguise.
 
 ## Decorator as Interceptor with Castle DynamicProxy
 
-[Explained here](Interception#decorator-with-castle-dynamicproxy)
+[Explained here](Interception.md#decorator-with-castle-dynamicproxy)
 
 
 ## Doing the interesting things with decorators

docs/DryIoc.Docs/Decorators.md

@@ -22,7 +22,7 @@
     - [Reusing the scoped service from the parent scope](#reusing-the-scoped-service-from-the-parent-scope)
 
 
-[FactoryMethod]:SelectConstructorOrFactoryMethod#factory-method-instead-of-constructor
+[FactoryMethod]:SelectConstructorOrFactoryMethod.md#factory-method-instead-of-constructor
 
 ## Overview
 
@@ -535,7 +535,7 @@ class Nesting_decorators_of_wrapped_service
 
 DryIoc supports decorating of wrappers directly to adjust corresponding wrapper behavior, to add new functionality, to apply filtering, etc.
 
-Consider the decorating of [collection wrapper](Wrappers#ienumerable-or-array-of-a).
+Consider the decorating of [collection wrapper](Wrappers.md#ienumerable-or-array-of-a).
 Let`s say we want to change the default collection behavior and exclude keyed services from the result:
 
 ```cs 
@@ -646,7 +646,7 @@ Moreover, to complement the `RegisterInitializer` there is also a [`RegisterDisp
 
 ## Decorator as Interceptor with Castle DynamicProxy
 
-[Explained here](Interception#decorator-with-castle-dynamicproxy)
+[Explained here](Interception.md#decorator-with-castle-dynamicproxy)
 
 
 ## Doing the interesting things with decorators

docs/DryIoc.Docs/ExamplesContextBasedResolution.cs

@@ -13,7 +13,7 @@
 
 Here is [the discussion](https://github.com/autofac/Autofac/issues/644) and example  [how to inject log4net](https://gist.github.com/piers7/81724d51a7ca158d721e) in Autofac.
 
-In DryIoc we may use [strongly-typed Factory Method](SelectConstructorOrFactoryMethod#factory-method-instead-of-constructor) specification to register log4net.ILog:
+In DryIoc we may use [strongly-typed Factory Method](SelectConstructorOrFactoryMethod.md#factory-method-instead-of-constructor) specification to register log4net.ILog:
 
 ```cs md*/
 using DryIoc;

docs/DryIoc.Docs/ExamplesContextBasedResolution.md

@@ -12,7 +12,7 @@
 
 Here is [the discussion](https://github.com/autofac/Autofac/issues/644) and example  [how to inject log4net](https://gist.github.com/piers7/81724d51a7ca158d721e) in Autofac.
 
-In DryIoc we may use [strongly-typed Factory Method](SelectConstructorOrFactoryMethod#factory-method-instead-of-constructor) specification to register log4net.ILog:
+In DryIoc we may use [strongly-typed Factory Method](SelectConstructorOrFactoryMethod.md#factory-method-instead-of-constructor) specification to register log4net.ILog:
 
 ```cs 
 using DryIoc;

docs/DryIoc.Docs/Extensions/MefAttributedModel.cs

@@ -568,7 +568,7 @@ public Client([WithMetadata("b")]I it) { /* will import it as Y */}
 
 ## Exporting disposable transient
 
-The attributes described below correspond to the specific [DryIoc registration options](..\ReuseAndScopes#disposable-transient).
+The attributes described below correspond to the specific [DryIoc registration options](..\ReuseAndScopes.md#disposable-transient).
 
 By default exporting transient service implementing `IDisposable` will throw the exception,
 until the container-wide rule is set `Rules.WithoutThrowOnRegisteringDisposableTransient`.
@@ -613,7 +613,7 @@ To enable the tracking see the `TrackDisposableTransientAttribute` below.
 ### TrackDisposableTransient
 
 Exported disposable transient marked with this attributed will be tracked by container and disposed on disposing the tracking scope.
-The attribute corresponds to DryIoc registration option [trackDisposableTransient](..\ReuseAndScopes#disposable-transient)
+The attribute corresponds to DryIoc registration option [trackDisposableTransient](..\ReuseAndScopes.md#disposable-transient)
 
 ```cs md*/
 class Exporting_with_TrackDisposableTransient
@@ -644,23 +644,23 @@ [Test] public void Example()
 
 ### AsDecorator attribute
 
-Check the [Decorators](../Decorators#overview)
+Check the [Decorators](../Decorators.md#overview)
 
 ### AsWrapper attribute
 
-Check the [Wrappers](../Wrappers#overview)
+Check the [Wrappers](../Wrappers.md#overview)
 
 ## Other export options
 
 ### PreventDisposalAttribute
 
-Sets the registration option [preventDisposal](..\ReuseAndScopes#prevent-disposal-of-reused-service).
+Sets the registration option [preventDisposal](..\ReuseAndScopes.md#prevent-disposal-of-reused-service).
 
 ### WeaklyReferencedAttribute
 
-Set the registration option [weaklyReferenced](..\ReuseAndScopes#weakly-referenced-reused-service).
+Set the registration option [weaklyReferenced](..\ReuseAndScopes.md#weakly-referenced-reused-service).
 
 ### AsResolutionCall
 
-Set the registration option [asResolutionCall](..\RulesAndDefaultConventions#injecting-dependency-asresolutioncall).
+Set the registration option [asResolutionCall](..\RulesAndDefaultConventions.md#injecting-dependency-asresolutioncall).
 md*/

docs/DryIoc.Docs/Extensions/MefAttributedModel.md

@@ -546,7 +546,7 @@ class Using_WithMetadata
 
 ## Exporting disposable transient
 
-The attributes described below correspond to the specific [DryIoc registration options](..\ReuseAndScopes#disposable-transient).
+The attributes described below correspond to the specific [DryIoc registration options](..\ReuseAndScopes.md#disposable-transient).
 
 By default exporting transient service implementing `IDisposable` will throw the exception,
 until the container-wide rule is set `Rules.WithoutThrowOnRegisteringDisposableTransient`.
@@ -590,7 +590,7 @@ To enable the tracking see the `TrackDisposableTransientAttribute` below.
 ### TrackDisposableTransient
 
 Exported disposable transient marked with this attributed will be tracked by container and disposed on disposing the tracking scope.
-The attribute corresponds to DryIoc registration option [trackDisposableTransient](..\ReuseAndScopes#disposable-transient)
+The attribute corresponds to DryIoc registration option [trackDisposableTransient](..\ReuseAndScopes.md#disposable-transient)
 
 ```cs 
 class Exporting_with_TrackDisposableTransient
@@ -620,22 +620,22 @@ class Exporting_with_TrackDisposableTransient
 
 ### AsDecorator attribute
 
-Check the [Decorators](../Decorators#overview)
+Check the [Decorators](../Decorators.md#overview)
 
 ### AsWrapper attribute
 
-Check the [Wrappers](../Wrappers#overview)
+Check the [Wrappers](../Wrappers.md#overview)
 
 ## Other export options
 
 ### PreventDisposalAttribute
 
-Sets the registration option [preventDisposal](..\ReuseAndScopes#prevent-disposal-of-reused-service).
+Sets the registration option [preventDisposal](..\ReuseAndScopes.md#prevent-disposal-of-reused-service).
 
 ### WeaklyReferencedAttribute
 
-Set the registration option [weaklyReferenced](..\ReuseAndScopes#weakly-referenced-reused-service).
+Set the registration option [weaklyReferenced](..\ReuseAndScopes.md#weakly-referenced-reused-service).
 
 ### AsResolutionCall
 
-Set the registration option [asResolutionCall](..\RulesAndDefaultConventions#injecting-dependency-asresolutioncall).
+Set the registration option [asResolutionCall](..\RulesAndDefaultConventions.md#injecting-dependency-asresolutioncall).

docs/DryIoc.Docs/KindsOfChildContainer.cs

@@ -31,8 +31,8 @@ DryIoc has no "usual" notion of child and parent container.
 IContainer With(Rules rules, IScopeContext scopeContext, RegistrySharing registrySharing, IScope singletonScope);
 ```
 
-- `rules` are described in details [here](RulesAndDefaultConventions#Rules-per-Container)
-- `scopeContext` and `singletonScope` are described [here](ReuseAndScopes#scopecontext) 
+- `rules` are described in details [here](RulesAndDefaultConventions.md#Rules-per-Container)
+- `scopeContext` and `singletonScope` are described [here](ReuseAndScopes.md#scopecontext) 
 
 `RegistrySharing` is the `enum` to specify how to re-use the parent registry:
 ```cs
@@ -42,7 +42,7 @@ public enum RegistrySharing { Share, CloneButKeepCache, CloneAndDropCache }
 The enum member names are self-explanatory.
 
 __Note__: `OpenScope` is another way to create a new container from existing one, but a bit different from `With`.
-It is explained in details [here](ReuseAndScopes#incurrentscope).
+It is explained in details [here](ReuseAndScopes.md#incurrentscope).
 
 
 ## Facade

docs/DryIoc.Docs/KindsOfChildContainer.md

@@ -30,8 +30,8 @@ The signature of `IContainer.With` describes what can be changed:
 IContainer With(Rules rules, IScopeContext scopeContext, RegistrySharing registrySharing, IScope singletonScope);
 ```
 
-- `rules` are described in details [here](RulesAndDefaultConventions#Rules-per-Container)
-- `scopeContext` and `singletonScope` are described [here](ReuseAndScopes#scopecontext) 
+- `rules` are described in details [here](RulesAndDefaultConventions.md#Rules-per-Container)
+- `scopeContext` and `singletonScope` are described [here](ReuseAndScopes.md#scopecontext) 
 
 `RegistrySharing` is the `enum` to specify how to re-use the parent registry:
 ```cs
@@ -41,7 +41,7 @@ public enum RegistrySharing { Share, CloneButKeepCache, CloneAndDropCache }
 The enum member names are self-explanatory.
 
 __Note__: `OpenScope` is another way to create a new container from existing one, but a bit different from `With`.
-It is explained in details [here](ReuseAndScopes#incurrentscope).
+It is explained in details [here](ReuseAndScopes.md#incurrentscope).
 
 
 ## Facade

docs/DryIoc.Docs/RegisterResolve.cs

@@ -277,14 +277,14 @@ It has an interesting property `DefaultKey.RegistrationOrder`. More on keyed reg
 
 There are also a couple of ways to select a specific registration and avoid an exception in `Resolve<ICommand>`:
 
-- Using [condition](SpecifyDependencyAndPrimitiveValues#registering-with-condition): 
+- Using [condition](SpecifyDependencyAndPrimitiveValues.md#registering-with-condition): 
 `container.Register<ICommand, GetCommand>(setup: Setup.With(condition: req => req.IsResolutionRoot))` 
 and for the rest of registrations to specify opposite condition, e.g. `condition: r => !r.IsResolutionRoot`.
 - Using specific metadata type (`CommandId` enum) and resolving as `Meta<,>` wrapper: 
 `container.Register<ICommand, GetCommand>(setup: Setup.With(metadata: CommandId.Get));` 
 and then resolving as `container.Resolve<IEnumerable<Meta<ICommand, CommandId>>>().Where(m => m.Metadata == CommandId.Get))`
-- Using [reuse bound to specific parent scope](ReuseAndScopes#reuseinresolutionscopeof) 
-or to [named scope](ReuseAndScopes#reuseincurrentnamedscope-and-reuseinthread).
+- Using [reuse bound to specific parent scope](ReuseAndScopes.md#reuseinresolutionscopeof) 
+or to [named scope](ReuseAndScopes.md#reuseincurrentnamedscope-and-reuseinthread).
 - Registering with `serviceKey`.
 
 
@@ -772,8 +772,8 @@ public CheerfulService(GreetingsProvider greetingsProvider)
 1. Memory leaks by capturing variables into delegate closure and keeping them for a container lifetime.
 2. Delegate is the black box for Container, mostly because it should use the `Resolve` call inside to resolve the dependency cutting of the object graph analysis, which makes it hard to find type mismatches or diagnose other potential problems. Among the un-catched problems are:
 
-    - [Recursive Dependency](ErrorDetectionAndResolution#RecursiveDependencyDetected)
-    - [Captive Dependency](ErrorDetectionAndResolution#using-validate-to-check-for-captive-dependency)
+    - [Recursive Dependency](ErrorDetectionAndResolution.md#RecursiveDependencyDetected)
+    - [Captive Dependency](ErrorDetectionAndResolution.md#using-validate-to-check-for-captive-dependency)
 
 Therefore, try to use it only as a last resort. DryIoc has plenty of tools to cover for custom delegate in more effective way. 
 The alternative would be a [FactoryMethod](ConstructorSelection).
@@ -786,7 +786,7 @@ It solves the two problems mentioned in the [RegisterDelegate](#registerdelegate
 it **injects** the requested dependencies as a delegate arguments so there is no need in calling `Resolve` inside.
 
 - The dependencies injection and their lifetime is controlled by container
-- There is no black-box service location involved and both [Recursive Dependency](ErrorDetectionAndResolution#RecursiveDependencyDetected) and [Captive Dependency](ErrorDetectionAndResolution#using-validate-to-check-for-captive-dependency) problems are catched by container.
+- There is no black-box service location involved and both [Recursive Dependency](ErrorDetectionAndResolution.md#RecursiveDependencyDetected) and [Captive Dependency](ErrorDetectionAndResolution.md#using-validate-to-check-for-captive-dependency) problems are catched by container.
 
 The example:
 ```cs md*/

docs/DryIoc.Docs/RegisterResolve.md

@@ -276,14 +276,14 @@ __Note:__ When resolving collection of multiple defaults, it always ordered in r
 
 There are also a couple of ways to select a specific registration and avoid an exception in `Resolve<ICommand>`:
 
-- Using [condition](SpecifyDependencyAndPrimitiveValues#registering-with-condition): 
+- Using [condition](SpecifyDependencyAndPrimitiveValues.md#registering-with-condition): 
 `container.Register<ICommand, GetCommand>(setup: Setup.With(condition: req => req.IsResolutionRoot))` 
 and for the rest of registrations to specify opposite condition, e.g. `condition: r => !r.IsResolutionRoot`.
 - Using specific metadata type (`CommandId` enum) and resolving as `Meta<,>` wrapper: 
 `container.Register<ICommand, GetCommand>(setup: Setup.With(metadata: CommandId.Get));` 
 and then resolving as `container.Resolve<IEnumerable<Meta<ICommand, CommandId>>>().Where(m => m.Metadata == CommandId.Get))`
-- Using [reuse bound to specific parent scope](ReuseAndScopes#reuseinresolutionscopeof) 
-or to [named scope](ReuseAndScopes#reuseincurrentnamedscope-and-reuseinthread).
+- Using [reuse bound to specific parent scope](ReuseAndScopes.md#reuseinresolutionscopeof) 
+or to [named scope](ReuseAndScopes.md#reuseincurrentnamedscope-and-reuseinthread).
 - Registering with `serviceKey`.
 
 
@@ -771,8 +771,8 @@ Though powerful, registering delegate may lead to the problems:
 1. Memory leaks by capturing variables into delegate closure and keeping them for a container lifetime.
 2. Delegate is the black box for Container, mostly because it should use the `Resolve` call inside to resolve the dependency cutting of the object graph analysis, which makes it hard to find type mismatches or diagnose other potential problems. Among the un-catched problems are:
 
-    - [Recursive Dependency](ErrorDetectionAndResolution#RecursiveDependencyDetected)
-    - [Captive Dependency](ErrorDetectionAndResolution#using-validate-to-check-for-captive-dependency)
+    - [Recursive Dependency](ErrorDetectionAndResolution.md#RecursiveDependencyDetected)
+    - [Captive Dependency](ErrorDetectionAndResolution.md#using-validate-to-check-for-captive-dependency)
 
 Therefore, try to use it only as a last resort. DryIoc has plenty of tools to cover for custom delegate in more effective way. 
 The alternative would be a [FactoryMethod](ConstructorSelection).
@@ -785,7 +785,7 @@ It solves the two problems mentioned in the [RegisterDelegate](#registerdelegate
 it **injects** the requested dependencies as a delegate arguments so there is no need in calling `Resolve` inside.
 
 - The dependencies injection and their lifetime is controlled by container
-- There is no black-box service location involved and both [Recursive Dependency](ErrorDetectionAndResolution#RecursiveDependencyDetected) and [Captive Dependency](ErrorDetectionAndResolution#using-validate-to-check-for-captive-dependency) problems are catched by container.
+- There is no black-box service location involved and both [Recursive Dependency](ErrorDetectionAndResolution.md#RecursiveDependencyDetected) and [Captive Dependency](ErrorDetectionAndResolution.md#using-validate-to-check-for-captive-dependency) problems are catched by container.
 
 The example:
 ```cs 

docs/DryIoc.Docs/RequiredServiceType.cs

@@ -236,7 +236,7 @@ public void Example()
 
 ## Works with IEnumerable and collection wrappers
 
-[IEnumerable and the rest of supported collection types]((Wrappers#ienumerable-or-array-of-a)) are also Wrappers, 
+[IEnumerable and the rest of supported collection types]((Wrappers.md#ienumerable-or-array-of-a)) are also Wrappers, 
 so you may expect required service type to work with them too:
 ```cs md*/
 class Required_service_type_in_collection

docs/DryIoc.Docs/RequiredServiceType.md

@@ -235,7 +235,7 @@ Here in `Arg.Of<Lazy<object>, IFoo>()` DryIoc will look for required service typ
 
 ## Works with IEnumerable and collection wrappers
 
-[IEnumerable and the rest of supported collection types]((Wrappers#ienumerable-or-array-of-a)) are also Wrappers, 
+[IEnumerable and the rest of supported collection types]((Wrappers.md#ienumerable-or-array-of-a)) are also Wrappers, 
 so you may expect required service type to work with them too:
 ```cs 
 class Required_service_type_in_collection

docs/DryIoc.Docs/ReuseAndScopes.cs

@@ -54,10 +54,10 @@ One type of reuse is well known in software development as [Singleton](http://en
 
 You can create your own reuse by implementing `IReuse` interface.
 
-Container uses Scopes ([see below](ReuseAndScopes#what-scope-is)) to 
+Container uses Scopes ([see below](ReuseAndScopes.md#what-scope-is)) to 
 store resolved services of non-Transient reuse.
 Scope implements `IDisposable` and when disposed will dispose reused disposable services. You may prevent service disposal 
-via [setup option](ReuseAndScopes#prevent-disposal-of-reused-service).
+via [setup option](ReuseAndScopes.md#prevent-disposal-of-reused-service).
 
 __Note:__ Service disposal is always taken in the reverse registration order.
 
@@ -698,7 +698,7 @@ class Dependency : IDisposable
 
 ### Own the resolution scope disposal
 
-You else may get in control of disposing the resolution scope by injecting the `IResolverContext` ([automatically provided for you by Container](RulesAndDefaultConventions#implicitly-available-services)) 
+You else may get in control of disposing the resolution scope by injecting the `IResolverContext` ([automatically provided for you by Container](RulesAndDefaultConventions.md#implicitly-available-services)) 
 which holds the current scope and then dispose it manually.
 
 ```cs md*/