README.md in fluent-plugin-ec2-metadata-0.0.5 vs README.md in fluent-plugin-ec2-metadata-0.0.6

@@ -1,8 +1,8 @@
-# fluent-plugin-ec2-metadata, a plugin for [Fluentd](http://fluentd.org)
+# fluent-plugin-ec2-metadata
 
-Fluentd plugin to add ec2 metadata fields to a event record
+[Fluentd](http://fluentd.org) plugin to add ec2 metadata fields to a event record
 
 ## Installation
 Use RubyGems:
 
     gem install fluent-plugin-ec2-metadata
@@ -54,15 +54,16 @@
 * ${tag_parts} input tag splitted by '.'. you can use it like `${tag_parts[0]}` or `${tag_parts[-1]}`
 * ${instance_id} instance id
 * ${instance_type} instance type
 * ${availability_zone} availability zone
 * ${region} region
+* ${mac} MAC address
+* ${vpc_id} vpc id
+* ${subnet_id} subnet id
 
 The followings are available when you define `aws_key_id` and `aws_sec_key`(or define IAM Policy):
 
-* ${vpc_id} vpc id
-* ${subnet_id} subnet id
 * ${tagset_xxx} EC2 tag (e.g. tagset_name is replaced by the value of Key = Name)
 
 The following is an example for a minimal IAM policy needed to ReadOnlyAccess to EC2.
 
 ```
@@ -95,11 +96,11 @@
     }
   ]
 }
 ```
 
-Refer to the {AWS documentation}[http://docs.aws.amazon.com/IAM/latest/UserGuide/ExampleIAMPolicies.html] for example policies.
-Using {IAM roles}[http://docs.aws.amazon.com/IAM/latest/UserGuide/WorkingWithRoles.html] with a properly configured IAM policy are preferred over embedding access keys on EC2 instances.
+Refer to the [AWS documentation](http://docs.aws.amazon.com/IAM/latest/UserGuide/ExampleIAMPolicies.html) for example policies.
+Using [IAM roles](http://docs.aws.amazon.com/IAM/latest/UserGuide/WorkingWithRoles.html) with a properly configured IAM policy are preferred over embedding access keys on EC2 instances.
 
 ## Contributing
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)