fix typos and update the blog title

Signed-off-by: Yingrong Zhao <yingrong.zhao@gmail.com>

docs/content/blog/persist-sensitive-data-safely.md

@@ -1,5 +1,5 @@
 ---
-title: "New Secret Plugin Protocol"
+title: "Upgrade your plugins to securely store sensitive data"
 description: "Learn how to keep your sensitive data generated by Porter safe and sound"
 date: "2022-05-31"
 authorname: "Yingrong Zhao"
@@ -14,7 +14,7 @@ summary: |
 As Porter approaches a v1.0.0 release, we have made an improvement in Porter to make sure any sensitive data generated or referenced by Porter is stored in a secure location.
 The newly updated secret plugin protocol enables Porter to securely store sensitive data in an external secret store instead of in Porter's database.
 
-Previously Porter only uses plugins for retrieving secrets from a secret store. When it comes to storing data generated by bundles, Porter uses storage plugins like Mongo as its backend database solution. If a sensitive data, such as a database connection string, were generated by a bundle, it would be stored in a Mongo database in plain text.
+Previously Porter only uses plugins for retrieving secrets from a secret store. When it comes to storing data generated by bundles, Porter uses storage plugins like Mongo as its backend database solution. If sensitive data, such as a database connection string, were generated by a bundle, it would be stored in a Mongo database in plain text.
 Now Porter requires users to configure a secret store to hold any data that has been marked as sensitive by the bundle. 
 
 Let's walk through how to utilize this new feature by updating your Porter configuration file and selecting an appropriate secret plugin. 
@@ -60,7 +60,7 @@ Hello, installing example-bundle with password: *******
 execution completed successfully!
 ```
 
-If you inspect your Porter's database, it stores a reference to the sensitive data that was saved in the configured secret store. Porter no longer stores the sensitive data in its database.
+If you inspect Porter's database, it stores a reference to the sensitive data that was saved in the configured secret store. Porter no longer stores the sensitive data in its database.
 
 Instead, we can find our "password" in our filesystem plugin. In your PORTER_HOME directory, you should find a subdirectory named `secrets`. Each file under this directory contains the sensitive value corresponding to a sensitive parameter or sensitive output from a run of a bundle.