Skip to content
Browse files

Fixing PSR-0 link to point to the proper github url

  • Loading branch information...
1 parent 8af542f commit 55ed24e85f90c6cb408233f3edd37bee2cc4452a @Howard3 Howard3 committed
Showing with 2 additions and 2 deletions.
  1. +1 −1 en/extending-lithium/third-party-libraries.wiki
  2. +1 −1 jp/02_lithium_basics/01_new_in_php_5.3.wiki
View
2 en/extending-lithium/third-party-libraries.wiki
@@ -4,7 +4,7 @@ Lithium applications are made up of collections of _libraries_. A library is any
## Basics
-Libraries are managed by the `lithium\core\Libraries` class, which handles auto-loading, service location, and introspecting available classes. When loading classes, Lithium assumes a [PSR-0 compatible](http://groups.google.com/group/php-standards/web/psr-0-final-proposal) class mapping structure. For more information, see the [documentation for the `Libraries` class](http://lithify.me/docs/lithium/core/Libraries).
+Libraries are managed by the `lithium\core\Libraries` class, which handles auto-loading, service location, and introspecting available classes. When loading classes, Lithium assumes a [PSR-0 compatible](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md) class mapping structure. For more information, see the [documentation for the `Libraries` class](http://lithify.me/docs/lithium/core/Libraries).
The default Lithium distribution ships with two `libraries` directories: one located at the root of the distribution, and one located in the `app` folder (or any application you generate with the console tooling). Libraries can be installed into either of these directories, and both are used interchangeably throughout this guide. The global `libraries` directory is intended for libraries which are shared across multiple applications, whereas the local directory is intended for application-specific ones, and will override the global directory in the event of a conflict.
View
2 jp/02_lithium_basics/01_new_in_php_5.3.wiki
@@ -23,7 +23,7 @@ class PostsController extends \lithium\action\Controller {
Pretty straightforward. Using namespaces keeps your application's classes separate from the Lithium core and third-party plugins, allowing for commonly used class names (File, Folder, etc.) to be used in both places.
-Lithium classes also follow the [PHP Standards Working Group namespace standard](http://groups.google.com/group/php-standards/web/psr-0-final-proposal) in order allow for easy autoloading of class file, and cross-library interoperability. This keeps your class files clean from messy include statements.
+Lithium classes also follow the [PHP Standards Working Group namespace standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md) in order allow for easy autoloading of class file, and cross-library interoperability. This keeps your class files clean from messy include statements.
## Anonymous Functions, Lambdas & Closures

0 comments on commit 55ed24e

Please sign in to comment.
Something went wrong with that request. Please try again.