Minor markdown style updates

Author: weierophinney

DEVELOPMENT_README.txt renamed to DEVELOPMENT_README.md

@@ -3,18 +3,18 @@ INSTALLATION
 
 Zend Framework requires no special installation steps. Simply download the framework,
 extract it to the folder you would like to keep it in, and add the library directory
-to your PHP include_path. To use components in the extras library, add the extras/library
-directory to your PHP include_path, as well.
-If you would like to use Zend_Tool, simply add bin/zf.bat (for Windows) or
-bin/zf.sh (for anything else) to your system executable path.
+to your PHP `include_path`. To use components in the extras library, add the extras/library
+directory to your PHP `include_path`, as well.
+If you would like to use `Zend_Tool`, simply add `bin/zf.bat` (for Windows) or
+`bin/zf.sh` (for anything else) to your system executable path.
 
 SYSTEM REQUIREMENTS
 -------------------
 
 Zend Framework requires PHP 5.2.11 or later. Please see the system requirements
 appendix for more detailed information:
 
-http://framework.zend.com/manual/en/requirements.html
+- http://framework.zend.com/manual/en/requirements.html
 
 DEVELOPMENT VERSIONS
 --------------------
@@ -38,50 +38,50 @@ of the following methods:
 
   The URL for the the Zend Framework 1.X git repository is:
 
-  https://github.com/zendframework/zf1
+  - https://github.com/zendframework/zf1
 
   For more information about git, please see the official website:
 
-  http://git-scm.com
+  - http://git-scm.com
 
 * Using Subversion. You may pin an svn:externals definition to our repository.
   For versions prior to 1.12.0, use the following URLs:
 
-  http://framework.zend.com/svn/framework/standard/branches/release-1.{minor version}
-  http://framework.zend.com/svn/framework/standard/tags/release-1.{minor version}.{maintenance version}
-  http://framework.zend.com/svn/framework/extras/branches/release-1.{minor version}
+  - http://framework.zend.com/svn/framework/standard/branches/release-1.{minor version}
+  - http://framework.zend.com/svn/framework/standard/tags/release-1.{minor version}.{maintenance version}
+  - http://framework.zend.com/svn/framework/extras/branches/release-1.{minor version}
 
   For versions 1.12.0 and on, use the following URLs:
 
-  https://github.com/zendframework/zf1/trunk (development version)
-  https://github.com/zendframework/zf1/tags/release-1.12.{maintenance version}
-  https://github.com/zendframework/zf1-extras/trunk
+  - https://github.com/zendframework/zf1/trunk (development version)
+  - https://github.com/zendframework/zf1/tags/release-1.12.{maintenance version}
+  - https://github.com/zendframework/zf1-extras/trunk
 
   For more information on subversion, please visit the official website:
 
-  http://subversion.apache.org/
+  - http://subversion.apache.org/
 
 CONFIGURING THE INCLUDE PATH
 ----------------------------
 
 Once you have a copy of Zend Framework available, your application will need to
 access the framework classes. Though there are several ways to achieve this, your
-PHP include_path needs to contain the path to the Zend Framework classes under the
-/library directory in this distribution. You can find out more about the PHP
-include_path configuration directive here:
+PHP `include_path` needs to contain the path to the Zend Framework classes under the
+`/library` directory in this distribution. You can find out more about the PHP
+`include_path` configuration directive here:
 
-http://www.php.net/manual/en/ini.core.php#ini.include-path
+- http://www.php.net/manual/en/ini.core.php#ini.include-path
 
 Instructions on how to change PHP configuration directives can be found here:
 
-http://www.php.net/manual/en/configuration.changes.php
+- http://www.php.net/manual/en/configuration.changes.php
 
 GETTING STARTED
 ---------------
 
 A great place to get up-to-speed quickly is the Zend Framework QuickStart:
 
-http://framework.zend.com/docs/quickstart
+- http://framework.zend.com/docs/quickstart
 
 The QuickStart covers some of the most commonly used components of ZF. Since
 Zend Framework is designed with a use-at-will architecture and components are

INSTALL.txt renamed to INSTALL.md

@@ -12,23 +12,23 @@ review.
 
 ### Option 1: GitHub
 
- 1. Setup a GitHub account (http://github.com/), if you haven't yet
- 2. Fork the ZF1 repository (http://github.com/zendframework/zf1)
- 3. Clone your fork locally and enter it (use your own GitHub username
-    in the statement below)
+1. Setup a GitHub account (http://github.com/), if you haven't yet
+2. Fork the ZF1 repository (http://github.com/zendframework/zf1)
+3. Clone your fork locally and enter it (use your own GitHub username
+   in the statement below)
 
-    ```sh
-    % git clone [email protected]:<username>/zf1.git
-    % cd zf2
-    ```
+   ```sh
+   % git clone [email protected]:<username>/zf1.git
+   % cd zf2
+   ```
 
- 4. Add a remote to the canonical ZF repository, so you can keep your fork
-    up-to-date:
+4. Add a remote to the canonical ZF repository, so you can keep your fork
+   up-to-date:
 
-    ```sh
-    % git remote add zf1 https://github.com/zendframework/zf1.git
-    % git fetch zf1
-    ```
+   ```sh
+   % git remote add zf1 https://github.com/zendframework/zf1.git
+   % git fetch zf1
+   ```
 
 ### Option 2: Personal Repository
 
@@ -38,38 +38,38 @@ own repository.  If you go this route, we will assume you have the knowledge to
 do so, or know where to obtain it. We will not assist you in setting up such a
 repository.
 
- 1.  Create a new repository
+1. Create a new repository
 
-    ```sh
-    % git init
-    ```
+   ```sh
+   % git init
+   ```
 
- 2. Add an "origin" remote pointing to your gitosis/gitolite repo:
+2. Add an "origin" remote pointing to your gitosis/gitolite repo:
 
-    ```sh
-    % git remote add origin git://yourdomain/yourrepo.git
-    ```
+   ```sh
+   % git remote add origin git://yourdomain/yourrepo.git
+   ```
 
- 3. Add a remote for the ZF repository and fetch it
+3. Add a remote for the ZF repository and fetch it
 
-    ```sh
-    % git remote add zf1 https://github.com/zendframework/zf1.git
-    % git fetch zf1
-    ```
+   ```sh
+   % git remote add zf1 https://github.com/zendframework/zf1.git
+   % git fetch zf1
+   ```
 
- 4. Create a new branch for the ZF repository (named "zf/master" here)
+4. Create a new branch for the ZF repository (named "zf/master" here)
 
-    ```sh
-    % git checkout -b zf/master zf1/master
-    ```
+   ```sh
+   % git checkout -b zf/master zf1/master
+   ```
 
- 5. Create your master branch off the ZF branch, and push to your
-    repository
+5. Create your master branch off the ZF branch, and push to your
+   repository
 
-    ```sh
-    % git checkout -b master
-    % git push origin HEAD:master
-    ```
+   ```sh
+   % git checkout -b master
+   % git push origin HEAD:master
+   ```
 
 ## Contributor License Agreement and your git configuration
 
@@ -117,12 +117,12 @@ as of merging your changes into the canonical repository.
 
 A typical work flow will then consist of the following:
 
- 1. Create a new local branch based off your master branch.
- 2. Switch to your new local branch. (This step can be combined with the
-    previous step with the use of `git checkout -b`.)
- 3. Do some work, commit, repeat as necessary.
- 4. Push the local branch to your remote repository.
- 5. Send a pull request.
+1. Create a new local branch based off your master branch.
+2. Switch to your new local branch. (This step can be combined with the
+   previous step with the use of `git checkout -b`.)
+3. Do some work, commit, repeat as necessary.
+4. Push the local branch to your remote repository.
+5. Send a pull request.
 
 The mechanics of this process are actually quite trivial. Below, we will
 create a branch for fixing an issue in the tracker.
@@ -160,13 +160,13 @@ your repository, select the branch you just created, and then select the
 If using your own repository - or even if using GitHub - you can send an
 email indicating you have changes to pull:
 
- -  Send to <[email protected]>
+- Send to <[email protected]>
 
- -  In your message, specify:
-     -  The URL to your repository (e.g., `git://mwop.net/zf1.git`)
-     -  The branch containing the changes you want pulled (e.g., `zf9295`)
-     -  The nature of the changes (e.g., `implements
-        Zend_Service_Twitter`, `fixes ZF-9295`, etc.)
+- In your message, specify:
+  - The URL to your repository (e.g., `git://mwop.net/zf1.git`)
+  - The branch containing the changes you want pulled (e.g., `zf9295`)
+  - The nature of the changes (e.g., `implements
+    Zend_Service_Twitter`, `fixes ZF-9295`, etc.)
 
 ### What branch to issue the pull request against?
 
@@ -186,24 +186,23 @@ get a ton of branches both locally and on your remote.
 Once you know that your changes have been accepted to the master
 repository, we suggest doing some cleanup of these branches.
 
- -  Local branch cleanup
+- Local branch cleanup
 
-    ```sh
-    % git branch -d <branchname>
-    ```
-
- -  Remote branch removal
+  ```sh
+  % git branch -d <branchname>
+  ```
 
-    ```sh
-    % git push origin :<branchname>
-    ```
+- Remote branch removal
 
+  ```sh
+  % git push origin :<branchname>
+  ```
 
 ## FEEDS AND EMAILS
 
 RSS feeds may be found at:
 
-`https://github.com/zendframework/zf1/commits/<branch>.atom`
+- `https://github.com/zendframework/zf1/commits/<branch>.atom`
 
 where &lt;branch&gt; is a branch in the repository.
 

README-GIT.md

@@ -211,7 +211,7 @@ http://framework.zend.com/manual/en/requirements.html
 INSTALLATION
 ============
 
-Please see [INSTALL.txt](INSTALL.txt).
+Please see [INSTALL.md](INSTALL.md).
 
 REPOSITORY HISTORY
 ==================
@@ -223,25 +223,31 @@ and only contains the tags for the 1.12 series. If you would like an older
 version, you may access the subversion repository linked above, or download an
 older version from http://framework.zend.com/downloads/archives.
 
+CONTRIBUTING
+============
+
+Please see [README-GIT.md](README-GIT.md) and
+[DEVELOPMENT_README.md](DEVELOPMENT_README.md).
+
 QUESTIONS AND FEEDBACK
 ======================
 
 Online documentation can be found at http://framework.zend.com/manual.
 Questions that are not addressed in the manual should be directed to the
 appropriate mailing list:
 
-http://framework.zend.com/wiki/display/ZFDEV/Mailing+Lists
+- http://framework.zend.com/wiki/display/ZFDEV/Mailing+Lists
 
 If you find code in this release behaving in an unexpected manner or
 contrary to its documented behavior, please create an issue in the Zend
 Framework issue tracker at:
 
-http://framework.zend.com/issues
+- https://github.com/zendframework/zf1/issues
 
 If you would like to be notified of new releases, you can subscribe to
 the fw-announce mailing list by sending a blank message to:
 
-[email protected].
+- [email protected].
 
 LICENSE
 =======