From 6ffc39a0adcc9513464099ff7d721fd6b9f678b1 Mon Sep 17 00:00:00 2001 From: Michael Foss Date: Tue, 19 Apr 2016 10:15:03 -0400 Subject: [PATCH] Convert documentation to ordered list Switch the dependency management documentation to an ordered list from a pseudo-ordered list. This has the benefit of using more structured markdown, and the added benefit of matching the "Suppose" list items with corresponding "Composer" list items. --- doc/00-intro.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/00-intro.md b/doc/00-intro.md index 72d69bc39..473f6bbb0 100644 --- a/doc/00-intro.md +++ b/doc/00-intro.md @@ -18,15 +18,13 @@ This idea is not new and Composer is strongly inspired by node's Suppose: -a) You have a project that depends on a number of libraries. - -b) Some of those libraries depend on other libraries. +1. You have a project that depends on a number of libraries. +1. Some of those libraries depend on other libraries. Composer: -c) Enables you to declare the libraries you depend on. - -d) Finds out which versions of which packages can and need to be installed, and +1. Enables you to declare the libraries you depend on. +1. Finds out which versions of which packages can and need to be installed, and installs them (meaning it downloads them into your project). See the [Basic usage](01-basic-usage.md) chapter for more details on declaring