readme.md in aws_recon-0.5.15 vs readme.md in aws_recon-0.5.16

@@ -18,10 +18,31 @@
 - More granular resource detail, including nested related resources in the output
 - Flexible output (console, JSON lines, plain JSON, file, S3 bucket, and standard out)
 - Efficient (multi-threaded, rate limited, automatic retries, and automatic result paging)
 - Easy to maintain and extend
 
+## Awesome companies using AWS Recon**
+
+- [Netflix](https://www.netflix.com/)
+- [Hashicorp](https://www.hashicorp.com/)
+- [Workday](https://www.workday.com/)
+- [Stripe](https://stripe.com/)
+- [PayPal](https://paypal.com/)
+- [Typeform](https://typeform.com/)
+- [Amazon Web Services](https://aws.amazon.com/)
+- [Plaid](https://plaid.com/)
+- [Expel](https://expel.io/)
+- [Mozilla](https://www.mozilla.org/)
+- [Bugcrowd](https://www.bugcrowd.com/)
+- [Dropbox](https://www.dropbox.com/)
+- [Pinterest](https://www.pinterest.com/)
+- [HackerOne](https://www.hackerone.com/)
+- [MuleSoft](https://www.mulesoft.com/)
+- [Drata](https://drata.com/)
+
+> ** usage does not imply endorsement
+
 ## Setup
 
 ### Requirements
 
 AWS Recon needs an AWS account role or credentials with `ReadOnlyAccess`. Full `AdministratorAccess` is over-privileged, but will work as well. The `SecurityAudit` policy is **not** sufficient as it omits access to many services.
@@ -53,17 +74,17 @@
 
 To run locally, first install the gem:
 
 ```
 $ gem install aws_recon
-Fetching aws_recon-0.5.2.gem
+Fetching aws_recon-0.5.16.gem
 Fetching aws-sdk-3.0.1.gem
 Fetching parallel-1.20.1.gem
 ...
 Successfully installed aws-sdk-3.0.1
 Successfully installed parallel-1.20.1
-Successfully installed aws_recon-0.5.2
+Successfully installed aws_recon-0.5.16
 ```
 
 Or add it to your Gemfile using `bundle`:
 
 ```
@@ -71,11 +92,11 @@
 Fetching gem metadata from https://rubygems.org/
 Resolving dependencies...
 ...
 Using aws-sdk 3.0.1
 Using parallel-1.20.1
-Using aws_recon 0.5.2
+Using aws_recon 0.5.16
 ```
 
 ## Usage
 
 AWS Recon will leverage any AWS credentials (see [requirements](#requirements)) currently available to the environment it runs in. If you are collecting from multiple accounts, you may want to leverage something like [aws-vault](https://github.com/99designs/aws-vault) to manage different credentials.
@@ -257,10 +278,10 @@
 Most users will want to limit collection to relevant services and regions. Running without any exclusions will attempt to collect all resources from all regions enabled for the account.
 
 ```
 $ aws_recon -h
 
-AWS Recon - AWS Inventory Collector (0.5.2)
+AWS Recon - AWS Inventory Collector (0.5.16)
 
 Usage: aws_recon [options]
     -r, --regions [REGIONS]          Regions to scan, separated by comma (default: all)
     -n, --not-regions [REGIONS]      Regions to skip, separated by comma (default: none)
     -s, --services [SERVICES]        Services to scan, separated by comma (default: all)