rename file

Author: webron

DEVELOPMENT.md

@@ -20,7 +20,7 @@ The specification _will change_ from the original 2.0 version.  We should typica
 ## Tracking Process
 
  - Use GitHub for all spec designs, use cases, and so on.
- - As with 2.0, the **human readable** document is the source of truth.  If using a JSON Schema again to document the spec, it is secondary to the human documentation.  The documentation should live in a *.md file, in parallel to the 2.0 document (versions/3.0.md for example).
+ - As with 2.0, the **human readable** document is the source of truth.  If using a JSON Schema again to document the spec, it is secondary to the human documentation.  The documentation should live in a *.md file, in parallel to the 2.0 document (versions/3.0.0.md for example).
  - The `master` branch shall remain the current, released OpenAPI Specification (i.e., 2.0).  We will work in an OpenAPI.next branch, which shall be described and linked to on the **default** README.md on master.
  - Examples of how something is described _currently_ vs. the proposed solution should accompany any change proposal.
  - New features should be done in feature branches which, upon approval, are merged into the OpenAPI.next branch.

README.md

@@ -17,7 +17,7 @@ Here you will find the information you need about the OpenAPI Specification, sim
 
 ## Current Version - 3.0
 
-The current version of the OpenAPI specification is [OpenAPI Specification 3.0](versions/3.0.md).
+The current version of the OpenAPI specification is [OpenAPI Specification 3.0](versions/3.0.0.md).
 
 ### Previous Versions
 
@@ -44,7 +44,7 @@ Development of the next version of the OpenAPI Specification is guided by the [T
 The Open API Initiative encourages participation from individuals and companies alike. 
 If you want to participate in the evolution of the OpenAPI Specification, consider taking the following actions:
 
-* Review the [current specification](versions/3.0.md). The human-readable markdown file _is the source of truth_ for the specification.
+* Review the [current specification](versions/3.0.0.md). The human-readable markdown file _is the source of truth_ for the specification.
 * Review the [development](DEVELOPMENT.md) process so you understand how the spec is evolving.
 * Check the [issues](https://github.com/OAI/OpenAPI-Specification/issues) and [pull requests](https://github.com/OAI/OpenAPI-Specification/pulls) to see if someone has already documented your idea or feedback on the specification. You can follow an existing conversation by adding a comment to the existing issue or PR.
 * Create an issue to describe a new concern. If possible, propose a solution.