Merge pull request #460 from resouer/dev

Update schematic description

Author: resouer

3.component_model.md

@@ -51,9 +51,13 @@ Here are the attributes that provide top-level information about the component d
 
 This section declares the schematic of a component that could be instantiated as part of an application in the later workflow.
 
-The OAM specification has no opinion or enforcement on the schematic itself as long as a JSON schema equivalent parameter list is defined. Though in order to make the specification implementable, several built-in approaches (`cue`, `helm`, `kube`) are defined as part of the specification for now.
+Note that OAM specification has no enforcement on how to implement the schematic as long as it could:
+  1. model a deployable unit;
+  2. expose a JSON schema or equivalent parameter list. 
 
-> Note: below sections may change in the future releases.
+Though in order to make the specification implementable, below schematic implementations (`cue`, `helm`, `kube`) are defined as part of the specification for now.
+
+> Note: hence below sections may change in the future releases.
 
 | Attribute | Type | Required | Default Value | Description |
 |-----------|------|----------|---------------|-------------|