Address bucketclass md comments

Signed-off-by: Ben <[email protected]>

doc/bucket-class-crd.md

@@ -5,7 +5,7 @@ The BucketClass CRD represents a structure that defines bucket policies relating
 Note that placement-bucketclass and namespace-bucketclass both use the same CR, and the difference lies inside the bucket class' `spec` section, more specifically the presence of either the `placementPolicy` or `namespacePolicy` key. 
 
 # Definitions
-- CRD: [noobaa.io_bucketclasses_crd.yaml](../deploy/crds/noobaa.io_bucketclasses_crd.yaml)
+- CRD: [noobaa.io_bucketclasses.yaml](../deploy/crds/noobaa.io_bucketclasses.yaml)
 - CR: [noobaa.io_v1alpha1_bucketclass_cr.yaml](../deploy/crds/noobaa.io_v1alpha1_bucketclass_cr.yaml)
 
 ## Placement Policy
@@ -28,10 +28,6 @@ Cache bucketclasses work by saving read objects in a chosen backingstore, which
 - Zero (`0`) - the cache will always compare the object's ETag before returning it. This option has a performance cost of getting the ETag from the remote target on each object read. This is the least performant option.
 - Positive (denoted in milliseconds, e.g. `3600000` equals to an hour) - once an object was read and saved in the cache, the chosen amount of time will have to pass prior to the object's ETag being compared again.
 
-# Definitions
-- CRD: [noobaa.io_bucketclasses_crd.yaml](../deploy/crds/noobaa.io_bucketclasses_crd.yaml)
-- CR: [noobaa.io_v1alpha1_bucketclass_cr.yaml](../deploy/crds/noobaa.io_v1alpha1_bucketclass_cr.yaml)
-
 ## Constraints:
 - A backing store name may appear in more than one bucket class but may not appear more than once in a certain bucket class.
 - The operator CLI currently only supports a single tier placement policy for a bucket class.