doc/design/milestone-0.0.7/csv-generation.md: formatting and add 'describe.yaml' file location assumption

Author: estroz

doc/design/milestone-0.0.7/csv-generation.md

@@ -53,7 +53,7 @@ import (
   ...
   appsv1 "k8s.io/api/apps/v1"
   rbacv1beta1 "k8s.io/api/rbac/v1beta1"
-	"github.com/operator-framework/operator-lifecycle-manager/pkg/api/apis/operators/v1alpha1"
+  "github.com/operator-framework/operator-lifecycle-manager/pkg/api/apis/operators/v1alpha1"
   "github.com/operator-framework/operator-lifecycle-manager/pkg/controller/install"
 )
 
@@ -123,7 +123,7 @@ func (us *CSVInstallStrategyUpdate) Apply(csv *v1alpha1.ClusterServiceVersion) e
 
 ### User-defined yaml objects
 
-Many CSV component objects cannot be populated using generated, non-SDK-specific manifests. These objects are mostly human-written, English metadata about the operator and various CRD's. A file, `describe.yaml`, with the following format should be written by a user with which the SDK can populate CSV objects:
+Many CSV component objects cannot be populated using generated, non-SDK-specific manifests. These objects are mostly human-written, English metadata about the operator and various CRD's. A file, `describe.yaml`, should be written by a user with which the SDK can populate CSV objects; this file should live in the `deploy` directory. `describe.yaml` will have the following format:
 
 ```yaml
 replaces: test-operator.0.1.0