edited the guid. fixed a huge bunch of links, hopefully all :)

Author: cebe

docs/guide/active-record.md

@@ -506,8 +506,8 @@ $order->subtotal = 100;
 $customer->link('orders', $order);
 ```
 
-The [[yii\db\Activerecord::link()|link()]] call above will set the `customer_id` of the order to be the primary key
-value of `$customer` and then call [[yii\db\Activerecord::save()|save()]] to save the order into database.
+The [[yii\db\ActiveRecord::link()|link()]] call above will set the `customer_id` of the order to be the primary key
+value of `$customer` and then call [[yii\db\ActiveRecord::save()|save()]] to save the order into database.
 
 
 Life Cycles of an ActiveRecord Object
@@ -520,33 +520,33 @@ method overriding and event handling mechanisms.
 When instantiating a new ActiveRecord instance, we will have the following life cycles:
 
 1. constructor
-2. [[yii\db\Activerecord::init()|init()]]: will trigger an [[yii\db\Activerecord::EVENT_INIT|EVENT_INIT]] event
+2. [[yii\db\ActiveRecord::init()|init()]]: will trigger an [[yii\db\ActiveRecord::EVENT_INIT|EVENT_INIT]] event
 
-When getting an ActiveRecord instance through the [[yii\db\Activerecord::find()|find()]] method, we will have the following life cycles:
+When getting an ActiveRecord instance through the [[yii\db\ActiveRecord::find()|find()]] method, we will have the following life cycles:
 
 1. constructor
-2. [[yii\db\Activerecord::init()|init()]]: will trigger an [[yii\db\Activerecord::EVENT_INIT|EVENT_INIT]] event
-3. [[yii\db\Activerecord::afterFind()|afterFind()]]: will trigger an [[yii\db\Activerecord::EVENT_AFTER_FIND|EVENT_AFTER_FIND]] event
+2. [[yii\db\ActiveRecord::init()|init()]]: will trigger an [[yii\db\ActiveRecord::EVENT_INIT|EVENT_INIT]] event
+3. [[yii\db\ActiveRecord::afterFind()|afterFind()]]: will trigger an [[yii\db\ActiveRecord::EVENT_AFTER_FIND|EVENT_AFTER_FIND]] event
 
-When calling [[yii\db\Activerecord::save()|save()]] to insert or update an ActiveRecord, we will have the following life cycles:
+When calling [[yii\db\ActiveRecord::save()|save()]] to insert or update an ActiveRecord, we will have the following life cycles:
 
-1. [[yii\db\Activerecord::beforeValidate()|beforeValidate()]]: will trigger an [[yii\db\Activerecord::EVENT_BEFORE_VALIDATE|EVENT_BEFORE_VALIDATE]] event
-2. [[yii\db\Activerecord::afterValidate()|afterValidate()]]: will trigger an [[yii\db\Activerecord::EVENT_AFTER_VALIDATE|EVENT_AFTER_VALIDATE]] event
-3. [[yii\db\Activerecord::beforeSave()|beforeSave()]]: will trigger an [[yii\db\Activerecord::EVENT_BEFORE_INSERT|EVENT_BEFORE_INSERT]] or [[yii\db\Activerecord::EVENT_BEFORE_UPDATE|EVENT_BEFORE_UPDATE]] event
+1. [[yii\db\ActiveRecord::beforeValidate()|beforeValidate()]]: will trigger an [[yii\db\ActiveRecord::EVENT_BEFORE_VALIDATE|EVENT_BEFORE_VALIDATE]] event
+2. [[yii\db\ActiveRecord::afterValidate()|afterValidate()]]: will trigger an [[yii\db\ActiveRecord::EVENT_AFTER_VALIDATE|EVENT_AFTER_VALIDATE]] event
+3. [[yii\db\ActiveRecord::beforeSave()|beforeSave()]]: will trigger an [[yii\db\ActiveRecord::EVENT_BEFORE_INSERT|EVENT_BEFORE_INSERT]] or [[yii\db\ActiveRecord::EVENT_BEFORE_UPDATE|EVENT_BEFORE_UPDATE]] event
 4. perform the actual data insertion or updating
-5. [[yii\db\Activerecord::afterSave()|afterSave()]]: will trigger an [[yii\db\Activerecord::EVENT_AFTER_INSERT|EVENT_AFTER_INSERT]] or [[yii\db\Activerecord::EVENT_AFTER_UPDATE|EVENT_AFTER_UPDATE]] event
+5. [[yii\db\ActiveRecord::afterSave()|afterSave()]]: will trigger an [[yii\db\ActiveRecord::EVENT_AFTER_INSERT|EVENT_AFTER_INSERT]] or [[yii\db\ActiveRecord::EVENT_AFTER_UPDATE|EVENT_AFTER_UPDATE]] event
 
-Finally when calling [[yii\db\Activerecord::delete()|delete()]] to delete an ActiveRecord, we will have the following life cycles:
+Finally when calling [[yii\db\ActiveRecord::delete()|delete()]] to delete an ActiveRecord, we will have the following life cycles:
 
-1. [[yii\db\Activerecord::beforeDelete()|beforeDelete()]]: will trigger an [[yii\db\Activerecord::EVENT_BEFORE_DELETE|EVENT_BEFORE_DELETE]] event
+1. [[yii\db\ActiveRecord::beforeDelete()|beforeDelete()]]: will trigger an [[yii\db\ActiveRecord::EVENT_BEFORE_DELETE|EVENT_BEFORE_DELETE]] event
 2. perform the actual data deletion
-3. [[yii\db\Activerecord::afterDelete()|afterDelete()]]: will trigger an [[yii\db\Activerecord::EVENT_AFTER_DELETE|EVENT_AFTER_DELETE]] event
+3. [[yii\db\ActiveRecord::afterDelete()|afterDelete()]]: will trigger an [[yii\db\ActiveRecord::EVENT_AFTER_DELETE|EVENT_AFTER_DELETE]] event
 
 
 Custom scopes
 -------------
 
-When [[yii\db\Activerecord::find()|find()]] or [[yii\db\Activerecord::findBySql()|findBySql()]] Active Record method is being called without parameters it returns an [[yii\db\Activerecord::yii\db\ActiveQuery|yii\db\ActiveQuery]]
+When [[yii\db\ActiveRecord::find()|find()]] or [[yii\db\ActiveRecord::findBySql()|findBySql()]] Active Record method is being called without parameters it returns an [[yii\db\ActiveRecord::yii\db\ActiveQuery|yii\db\ActiveQuery]]
 instance. This object holds all the parameters and conditions for a future query and also allows you to customize these
 using a set of methods that are called scopes. By default there is a good set of such methods some of which we've
 already used above: `where`, `orderBy`, `limit` etc.
@@ -657,8 +657,8 @@ When a few DB operations are related and are executed
 TODO: FIXME: WIP, TBD, https://github.com/yiisoft/yii2/issues/226
 
 ,
-[[yii\db\Activerecord::afterSave()|afterSave()]], [[yii\db\Activerecord::beforeDelete()|beforeDelete()]] and/or [[yii\db\Activerecord::afterDelete()|afterDelete()]] life cycle methods. Developer may come
-to the solution of overriding ActiveRecord [[yii\db\Activerecord::save()|save()]] method with database transaction wrapping or
+[[yii\db\ActiveRecord::afterSave()|afterSave()]], [[yii\db\ActiveRecord::beforeDelete()|beforeDelete()]] and/or [[yii\db\ActiveRecord::afterDelete()|afterDelete()]] life cycle methods. Developer may come
+to the solution of overriding ActiveRecord [[yii\db\ActiveRecord::save()|save()]] method with database transaction wrapping or
 even using transaction in controller action, which is strictly speaking doesn't seem to be a good
 practice (recall "skinny-controller / fat-model" fundamental rule).
 
@@ -686,7 +686,7 @@ class Product extends \yii\db\ActiveRecord
 }
 ```
 
-Overriding [[yii\db\Activerecord::save()|save()]] method:
+Overriding [[yii\db\ActiveRecord::save()|save()]] method:
 
 ```php
 

docs/guide/assets.md

@@ -2,9 +2,9 @@ Managing assets
 ===============
 
 An asset in Yii is a file that is included into the page. It could be CSS, JavaScript or
-any other file. Framework provides many ways to work with assets from basics such as adding `<script src="` tag
+any other file. Framework provides many ways to work with assets from basics such as adding `<script src="...">` tag
 for a file that is [handled by View](view.md) section to advanced usage such as publishing files that are not
-under webserve document root, resolving JavaScript dependencies or minifying CSS.
+under the webservers document root, resolving JavaScript dependencies or minifying CSS.
 
 Declaring asset bundle
 ----------------------
@@ -13,9 +13,15 @@ In order to publish some assets you should declare an asset bundle first. The bu
 directories to be published and their dependencies on other asset bundles.
 
 Both basic and advanced application templates contain `AppAsset` asset bundle class that defines assets required
-application wide. Let's review basic application asset bundle class:
+application wide. An asset bundle class always extends from [[yii\web\AssetBundle]].
+
+Let's review basic application's asset bundle class:
 
 ```php
+<?php
+
+use yii\web\AssetBundle as AssetBundle;
+
 class AppAsset extends AssetBundle
 {
 	public $basePath = '@webroot';

docs/guide/authorization.md

@@ -209,7 +209,7 @@ public function behaviors()
 }
 ```
 
-Another way is to call [[User::checkAccess()]] where appropriate.
+Another way is to call [[yii\web\User::checkAccess()]] where appropriate.
 
 ### Using DB-based storage for RBAC
 

docs/guide/basics.md

@@ -5,21 +5,22 @@ Basic concepts of Yii
 Component and Object
 --------------------
 
-Classes of the Yii framework usually extend from one of the two base classes [[Object]] and [[Component]].
+Classes of the Yii framework usually extend from one of the two base classes [[yii\base\Object]] and [[yii\base\Component]].
 These classes provide useful features that are added automatically to all classes extending from them.
 
-The `Object` class provides the [configuration and property feature](../api/base/Object.md).
-The `Component` class extends from `Object` and adds [event handling](events.md) and [behaviors](behaviors.md).
+The [[yii\base\Object|Object]] class provides the [configuration and property feature](../api/base/Object.md).
+The [[yii\base\Component|Component]] class extends from [[yii\base\Object|Object]] and adds
+[event handling](events.md) and [behaviors](behaviors.md).
 
-`Object` is usually used for classes that represent basic data structures while `Component` is used for
-application components and other classes that implement higher logic.
+[[yii\base\Object|Object]] is usually used for classes that represent basic data structures while
+[[yii\base\Component|Component]] is used for application components and other classes that implement higher logic.
 
 
 Object Configuration
 --------------------
 
-The [[Object]] class introduces a uniform way of configuring objects. Any descendant class
-of [[Object]] should declare its constructor (if needed) in the following way so that
+The [[yii\base\Object|Object]] class introduces a uniform way of configuring objects. Any descendant class
+of [[yii\base\Object|Object]] should declare its constructor (if needed) in the following way so that
 it can be properly configured:
 
 ```php

docs/guide/behaviors.md

@@ -9,8 +9,10 @@ code execution. Unlike [PHP's traits](http://www.php.net/traits), behaviors can
 Using behaviors
 ---------------
 
-A behavior can be attached to any class that extends from `Component`. In order to attach a behavior to a class, the component class must implement the `behaviors`
-method. As an example, Yii provides the `AutoTimestamp` behavior for automatically updating timestamp fields when saving an Active Record model:
+A behavior can be attached to any class that extends from [[yii\base\Component]]. In order to attach a behavior to a class,
+the component class must implement the `behaviors`
+method. As an example, Yii provides the [[yii\behaviors\AutoTimestamp|AutoTimestamp]] behavior for automatically updating timestamp
+fields when saving an [[yii\db\ActiveRecord|Active Record]] model:
 
 ```php
 class User extends ActiveRecord
@@ -32,7 +34,10 @@ class User extends ActiveRecord
 }
 ```
 
-In the above, the `class` value is a string representing the fully qualified behavior class name. All of the other key-value pairs represent corresponding public properties of the `AutoTimestamp` class, thereby customizing how the behavior functions.
+In the above, the `class` value is a string representing the fully qualified behavior class name.
+All of the other key-value pairs represent corresponding public properties of the [[yii\behaviors\AutoTimestamp|AutoTimestamp]]
+class, thereby customizing how the behavior functions.
+
 
 Creating your own behaviors
 ---------------------------

docs/guide/bootstrap-widgets.md

@@ -33,26 +33,26 @@ Yii widgets
 Most complex bootstrap components are wrapped into Yii widgets to allow more robust syntax and integrate with
 framework features. All widgets belong to `\yii\bootstrap` namespace:
 
-- Alert
-- Button
-- ButtonDropdown
-- ButtonGroup
-- Carousel
-- Collapse
-- Dropdown
-- Modal
-- Nav
-- NavBar
-- Progress
-- Tabs
+- [[yii\bootstrap\Alert|Alert]]
+- [[yii\bootstrap\Button|Button]]
+- [[yii\bootstrap\ButtonDropdown|ButtonDropdown]]
+- [[yii\bootstrap\ButtonGroup|ButtonGroup]]
+- [[yii\bootstrap\Carousel|Carousel]]
+- [[yii\bootstrap\Collapse|Collapse]]
+- [[yii\bootstrap\Dropdown|Dropdown]]
+- [[yii\bootstrap\Modal|Modal]]
+- [[yii\bootstrap\Nav|Nav]]
+- [[yii\bootstrap\NavBar|NavBar]]
+- [[yii\bootstrap\Progress|Progress]]
+- [[yii\bootstrap\Tabs|Tabs]]
 
 
 Using the .less files of Bootstrap directly
 -------------------------------------------
 
 If you want to include the [Bootstrap css directly in your less files](http://getbootstrap.com/getting-started/#customizing)
 you may need to disable the original bootstrap css files to be loaded.
-You can do this by setting the css property of the `BootstrapAsset` to be empty.
+You can do this by setting the css property of the [[yii\bootstrap\BootstrapAsset|BootstrapAsset]] to be empty.
 For this you need to configure the `assetManagner` application component as follows:
 
 ```php

docs/guide/caching.md

@@ -73,7 +73,7 @@ is a summary of the available cache components:
   [Zend Data Cache](http://files.zend.com/help/Zend-Server-6/zend-server.htm#data_cache_component.htm)
   as the underlying caching medium.
 
-Tip: because all these cache components extend from the same base class [[Cache]], one can switch to use
+Tip: because all these cache components extend from the same base class [[yii\caching\Cache]], one can switch to use
 a different type of cache without modifying the code that uses cache.
 
 Caching can be used at different levels. At the lowest level, we use cache to store a single piece of data,
@@ -92,25 +92,25 @@ Data Caching
 
 Data caching is about storing some PHP variable in cache and retrieving it later from cache. For this purpose,
 the cache component base class [[\yii\caching\Cache]] provides two methods that are used most of the time:
-[[set()]] and [[get()]]. Note, only serializable variables and objects could be cached successfully.
+[[yii\caching\Cache::set()|set()]] and [[yii\caching\Cache::get()|get()]]. Note, only serializable variables and objects could be cached successfully.
 
-To store a variable `$value` in cache, we choose a unique `$key` and call [[set()]] to store it:
+To store a variable `$value` in cache, we choose a unique `$key` and call [[yii\caching\Cache::set()|set()]] to store it:
 
 ```php
 Yii::$app->cache->set($key, $value);
 ```
 
 The cached data will remain in the cache forever unless it is removed because of some caching policy
 (e.g. caching space is full and the oldest data are removed). To change this behavior, we can also supply
-an expiration parameter when calling [[set()]] so that the data will be removed from the cache after
+an expiration parameter when calling [[yii\caching\Cache::set()|set()]] so that the data will be removed from the cache after
 a certain period of time:
 
 ```php
 // keep the value in cache for at most 45 seconds
 Yii::$app->cache->set($key, $value, 45);
 ```
 
-Later when we need to access this variable (in either the same or a different web request), we call [[get()]]
+Later when we need to access this variable (in either the same or a different web request), we call [[yii\caching\Cache::get()|get()]]
 with the key to retrieve it from cache. If the value returned is `false`, it means the value is not available
 in cache and we should regenerate it:
 
@@ -134,18 +134,20 @@ may be cached in the application. It is **NOT** required that the key is unique
 the cache component is intelligent enough to differentiate keys for different applications.
 
 Some cache storages, such as MemCache, APC, support retrieving multiple cached values in a batch mode,
-which may reduce the overhead involved in retrieving cached data. A method named [[mget()]] is provided
+which may reduce the overhead involved in retrieving cached data. A method named [[yii\caching\Cache::mget()|mget()]] is provided
 to exploit this feature. In case the underlying cache storage does not support this feature,
-[[mget()]] will still simulate it.
+[[yii\caching\Cache::mget()|mget()]] will still simulate it.
 
-To remove a cached value from cache, call [[delete()]]; and to remove everything from cache, call [[flush()]].
-Be very careful when calling [[flush()]] because it also removes cached data that are from other applications.
+To remove a cached value from cache, call [[yii\caching\Cache::delete()|delete()]]; and to remove everything from cache, call
+[[yii\caching\Cache::flush()|flush()]].
+Be very careful when calling [[yii\caching\Cache::flush()|flush()]] because it also removes cached data that are from
+other applications if the cache is shared among different applications.
 
-Note, because [[Cache]] implements `ArrayAccess`, a cache component can be used liked an array. The followings
+Note, because [[yii\caching\Cache]] implements `ArrayAccess`, a cache component can be used liked an array. The followings
 are some examples:
 
 ```php
-$cache = Yii::$app->getComponent('cache');
+$cache = Yii::$app->cache;
 $cache['var1'] = $value1;  // equivalent to: $cache->set('var1', $value1);
 $value2 = $cache['var2'];  // equivalent to: $value2 = $cache->get('var2');
 ```
@@ -157,10 +159,10 @@ are caching the content of some file and the file is changed, we should invalida
 content from the file instead of the cache.
 
 We represent a dependency as an instance of [[\yii\caching\Dependency]] or its child class. We pass the dependency
-instance along with the data to be cached when calling `set()`.
+instance along with the data to be cached when calling [[yii\caching\Cache::set()|set()]].
 
 ```php
-use yii\cache\FileDependency;
+use yii\caching\FileDependency;
 
 // the value will expire in 30 seconds
 // it may also be invalidated earlier if the dependent file is changed
@@ -172,12 +174,12 @@ get a false value, indicating the data needs to be regenerated.
 
 Below is a summary of the available cache dependencies:
 
-- [[\yii\cache\FileDependency]]: the dependency is changed if the file's last modification time is changed.
-- [[\yii\cache\GroupDependency]]: marks a cached data item with a group name. You may invalidate the cached data items
-  with the same group name all at once by calling [[\yii\cache\GroupDependency::invalidate()]].
-- [[\yii\cache\DbDependency]]: the dependency is changed if the query result of the specified SQL statement is changed.
-- [[\yii\cache\ChainedDependency]]: the dependency is changed if any of the dependencies on the chain is changed.
-- [[\yii\cache\ExpressionDependency]]: the dependency is changed if the result of the specified PHP expression is
+- [[\yii\caching\FileDependency]]: the dependency is changed if the file's last modification time is changed.
+- [[\yii\caching\GroupDependency]]: marks a cached data item with a group name. You may invalidate the cached data items
+  with the same group name all at once by calling [[\yii\caching\GroupDependency::invalidate()]].
+- [[\yii\caching\DbDependency]]: the dependency is changed if the query result of the specified SQL statement is changed.
+- [[\yii\caching\ChainedDependency]]: the dependency is changed if any of the dependencies on the chain is changed.
+- [[\yii\caching\ExpressionDependency]]: the dependency is changed if the result of the specified PHP expression is
   changed.
 
 ### Query Caching

docs/guide/console-migrate.md

@@ -103,7 +103,7 @@ by Yii with the corresponding types depended on your database management system.
 You can use them to write database independent migrations.
 For example `pk` will be replaced by `int(11) NOT NULL AUTO_INCREMENT PRIMARY KEY`
 for MySQL and `integer PRIMARY KEY AUTOINCREMENT NOT NULL` for sqlite.
-See documentation of [[QueryBuilder::getColumnType()]] for more details and a list
+See documentation of [[yii\db\QueryBuilder::getColumnType()]] for more details and a list
 of available types. You may also use the constants defined in [[\yii\db\Schema]] to
 define column types.