cleanup markdown docs across multiple files (#14296)

enable markdown-linter

docs/bucket/versioning/DESIGN.md

@@ -3,10 +3,10 @@
 ## Description of `xl.meta`
 
 `xl.meta` is a new self describing backend format used by MinIO to support AWS S3 compatible versioning.
-This file is the source of truth for each `version` at rest. `xl.meta` is a msgpack file serialized from a 
+This file is the source of truth for each `version` at rest. `xl.meta` is a msgpack file serialized from a
 well defined data structure. To understand `xl.meta` here are the few things to start with
 
-`xl.meta` carries first 8 bytes an XL header which describes the current format and the format version, 
+`xl.meta` carries first 8 bytes an XL header which describes the current format and the format version,
 allowing the unmarshaller's to automatically use the right data structures to parse the subsequent content in the stream.
 
 ### v1.0
@@ -43,6 +43,7 @@ Therefore, the metadata is wrapped as a binary array for easy skipping.
 - DeleteMarker (a versionId to capture the DELETE sequences implemented primarily for AWS spec compatibility)
 
 A sample msgpack-JSON `xl.meta`, you can debug the content inside `xl.meta` using [xl-meta.go](https://github.com/minio/minio/tree/master/docs/debugging#decoding-metadata) program.
+
 ```json
 {
   "Versions": [
@@ -92,7 +93,7 @@ Version 1.3 introduces changes to help with [faster metadata reads and updates](
 | versions        | msgp int                    | Number of versions following
 | header_1        | msgp bin array              | Header of version 1
 | metadata_1      | msgp bin array              | Metadata of version 1
-| ...header_n     | msgp bin array              | Header of last version 
+| ...header_n     | msgp bin array              | Header of last version
 | ...metadata_n   | msgp bin array              | Metadata of last version
 
 Each header contains a mspg array (tuple) encoded object:
@@ -102,11 +103,11 @@ xlHeaderVersion version == 1:
 ```
 //msgp:tuple xlMetaV2VersionHeader
 type xlMetaV2VersionHeader struct {
-	VersionID [16]byte  // Version UUID, raw.
-	ModTime   int64     // Unix nanoseconds.
-	Signature [4]byte   // Signature of metadata.
-	Type      uint8     // Type if the version
-	Flags     uint8
+ VersionID [16]byte  // Version UUID, raw.
+ ModTime   int64     // Unix nanoseconds.
+ Signature [4]byte   // Signature of metadata.
+ Type      uint8     // Type if the version
+ Flags     uint8
 }
 ```
 
@@ -114,9 +115,9 @@ The following flags are defined:
 
 ```
 const (
-	FreeVersion = 1 << 0
-	UsesDataDir = 1 << 1
-	InlineData  = 1 << 2
+ FreeVersion = 1 << 0
+ UsesDataDir = 1 << 1
+ InlineData  = 1 << 2
 )
 ```
 

docs/bucket/versioning/README.md

@@ -31,6 +31,7 @@ To permanently delete an object you need to specify the version you want to dele
 ![delete_version_id](https://raw.githubusercontent.com/minio/minio/master/docs/bucket/versioning/versioning_DELETE_versionEnabled_id.png)
 
 ## Concepts
+
 - All Buckets on MinIO are always in one of the following states: unversioned (the default) and all other existing deployments, versioning-enabled, or versioning-suspended.
 - Versioning state applies to all of the objects in the versioning enabled bucket. The first time you enable a bucket for versioning, objects in the bucket are thereafter always versioned and given a unique version ID.
 - Existing or newer buckets can be created with versioning enabled and eventually can be suspended as well. Existing versions of objects stay as is and can still be accessed using the version ID.
@@ -38,13 +39,16 @@ To permanently delete an object you need to specify the version you want to dele
 - **Versioning feature is only available in erasure coded and distributed erasure coded setups**.
 
 ## How to configure versioning on a bucket
+
 Each bucket created has a versioning configuration associated with it. By default bucket is unversioned as shown below
+
 ```
 <VersioningConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
 </VersioningConfiguration>
 ```
 
 To enable versioning, you send a request to MinIO with a versioning configuration with Status set to `Enabled`.
+
 ```
 <VersioningConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
   <Status>Enabled</Status>
@@ -52,6 +56,7 @@ To enable versioning, you send a request to MinIO with a versioning configuratio
 ```
 
 Similarly to suspend versioning set the configuration with Status set to `Suspended`.
+
 ```
 <VersioningConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
   <Status>Suspended</Status>
@@ -160,6 +165,7 @@ public class IsVersioningEnabled {
 ```
 
 ## Explore Further
+
 - [Use `minio-java` SDK with MinIO Server](https://docs.minio.io/docs/java-client-quickstart-guide.html)
 - [Object Lock and Immutablity Guide](https://docs.minio.io/docs/minio-bucket-object-lock-guide.html)
 - [MinIO Admin Complete Guide](https://docs.min.io/docs/minio-admin-complete-guide.html)