docs: convert unordered lists to ordered lists if appropriate

Some workflows are formatted as unordered lists. It's better to convert
these lists to ordered ones.

Signed-off-by: Satoru Takeuchi <satoru.takeuchi@gmail.com>

CONTRIBUTING.md

@@ -40,20 +40,20 @@ request and branch commits.
 
 ## Getting Started
 
-- Fork the repository on GitHub
-- Read the [install](INSTALL.md) for build and test instructions
-- Play with the project, submit bugs, submit patches!
+1. Fork the repository on GitHub
+1. Read the [install](INSTALL.md) for build and test instructions
+1. Play with the project, submit bugs, submit patches!
 
 ## Contribution Flow
 
 This is a rough outline of what a contributor's workflow looks like:
 
-- Create a branch from where you want to base your work (usually master).
-- Make your changes and arrange them in readable commits.
-- Make sure your commit messages are in the proper format (see below).
-- Push your changes to the branch in your fork of the repository.
-- Make sure all tests pass, and add any new tests as appropriate.
-- Submit a pull request to the original repository.
+1. Create a branch from where you want to base your work (usually master).
+1. Make your changes and arrange them in readable commits.
+1. Make sure your commit messages are in the proper format (see below).
+1. Push your changes to the branch in your fork of the repository.
+1. Make sure all tests pass, and add any new tests as appropriate.
+1. Submit a pull request to the original repository.
 
 For detailed contribution instructions, refer to the [development flow](Documentation/development-flow.md).