Edit of first blog post (#381)

* Edit of first blog post, and PR test for git newb

* Update 2021-10-18-announcing-lunasec.md

* Update 2021-10-18-announcing-lunasec.md

* Update 2021-10-18-announcing-lunasec.md

docs/blog/2021-10-18-announcing-lunasec.md

@@ -23,72 +23,74 @@ authors:
   ~
 -->
 We are proud to announce that LunaSec has hit Version 1.0 and has been publicly released on our 
-[GitHub](https://github.com/lunasec-io/lunasec) page. With this release, we've officially hit **stable** and we are now 
+[GitHub](https://github.com/lunasec-io/lunasec) page. With this release, we've officially hit **stable** and are now 
 offering enterprise and open-source support for LunaSec.
 
 AWS, NodeJS, and React is the fully supported stack at the moment, and now we are hard at work adding support for more environments.
 
-Please take a moment to learn about LunaSec by reading the rest of this post and trying the [example app](https://www.lunasec.io/docs/pages/overview/demo-app/overview/)(it's really easy).
+Please take a moment to learn about LunaSec by reading the rest of this post and trying the [example app](https://www.lunasec.io/docs/pages/overview/demo-app/overview/) (it's really easy).
 
 Read on....
 <!--truncate-->
 
 ## What problems does LunaSec solve?
-LunaSec is a data security platform that's designed to work alongside your software to make storing + managing sensitive
+LunaSec is a data security platform that's designed to work alongside your software to make storing and managing sensitive
 data much simpler.
 
 We started with a simple question: Why are so many companies constantly leaking data?
 
 As it turns out, that's actually a very nuanced and difficult question to answer. Most companies _do_ want to securely
-store their user's data. They don't want to experience a security breach. They just aren't able to because it's not easy
-to get right. Even large companies storing highly sensitive data suffer because of simple reasons like not
+store their user's data. They don't want to experience a security breach. They just aren't able to store user data securely because it's not easy
+to get right. Even large companies storing highly sensitive data suffer due to simple reasons like not
 [updating a dependency](https://arstechnica.com/information-technology/2017/09/massive-equifax-breach-caused-by-failure-to-patch-two-month-old-bug/)
 or because of [one engineer's actions](https://www.cnn.com/2019/07/29/business/capital-one-data-breach/index.html) 
 being able to bring the whole house of cards down.
 
-There has to be a better way to at least make it _harder_ for companies to be caught with their security pants down. It's embarrassing!
+There has to be a better way to at least make it _harder_ for companies to be caught with their pants down when it comes to security. It's embarrassing!
 
 ## What is LunaSec?
 LunaSec does a lot, but the main way it works is by replacing sensitive data with meaningless identifiers known as "Tokens". Think of a long
 random number like a UUID (eg, `lunasec-a215783b-1f0d-4e2a-8e53-76951b9c60fe`). Your code then only ever deals with these 
 Tokens directly. All sensitive data lives in a dedicated encrypted database that's managed by LunaSec.
 
-A lot of security products do that, but LunaSec builds more security on-top of that idea than anyone else,
+A lot of security products do that, but LunaSec builds more security ontop of that idea, more than anyone else,
 because a lot of other pieces are needed to make that encryption actually *secure*.
 
-### The problems are:
-1. Encryption by itself isn't very useful if somebody can simply query the Database and grab the decryption keys.
-2. You also need to be able to restrict access to decryption keys if you want to be able to meaningfully protect data.
-3. And then you need to have logic to determine who is authorized to decrypt data...
-4. And then you need a way to authenticate users to ensure your authorization logic can't be spoofed...
-5. But what if there is a bug in one of your dependencies? Does that bring down the security of the entire system? 
-6. Does every line of code need to go through a security review now? Do you need an approved list of dependencies and versions now?
-7. Implement org-wide security procedures that nobody understands or cares about because they're just developers trying to do their job... 
+### The problems are myriad:
+- Encryption by itself isn't very useful if somebody can simply query the Database and grab the decryption keys
+- You also need to be able to restrict access to decryption keys if you want to be able to meaningfully protect data
+- A logical system is required to determine who is authorized to decrypt data
+- A means of authenticating users to ensure your authorization logic can't be spoofed is necessary
+- A bug in one of your dependencies can bring down the security of the entire system
+
+
+How do you effectively address and mitigate such a litany of problems? Does every line of code need to go through a security review now? Do you need an approved list of dependencies and versions now? Does it become necessary to implement organization-wide security procedures that nobody understands or cares about because they're just developers trying to do their job... 
 
 ... You get the point!
 
+
 Once you start adding in all the necessary components to make a secure system, it becomes painful, fast. There
-is a lot of complexity to manage. It's simply too much complexity for most developers to deal with and still
-do their jobs. The incentives are just not aligned to have security forced onto teams.
+is a lot of complexity to manage. It's simply too much complexity for most developers to deal with while still
+doing their jobs. The incentives for security are just not aligned with having security forced onto teams.
 
 That's the problem we aim to solve with LunaSec: We've built a suite of software libraries and services that you can
 integrate directly into your code. They're designed in a way that enables you to split access to sensitive data away 
 from your code. That means you're free to develop software without security reviews while also still guaranteeing that 
 sensitive data remains safe.
 
-We made a few different levels of how far you want to integrate LunaSec.  The deeper you go, [the more protection from attacks you get](https://www.lunasec.io/docs/pages/overview/security/levels/). 
-When you need more protection, you can add integrate further.
+We made a few different levels for how far you may want to integrate LunaSec.  The deeper you go, [the more protection from attacks you get](https://www.lunasec.io/docs/pages/overview/security/levels/). 
+When you need more protection, you can integrate more protection.
 
 ## Why is LunaSec's approach unique?
 Our secret is simple: We're a team of Security Engineers that have also built and shipped production software. 
 We've been on both sides of the fence.
 
 Our approach is unique because we have seen how software exists in the real world. Unfortunately, software in the real
-world is painful and full of compromises. Those compromises degrade security over time and form cracks in the system.
+world is painful and full of compromises. These compromises degrade security over time and form cracks in the system.
 Eventually those cracks cascade and result in security issues like data leaks.
 
 With LunaSec, we hope to provide the tools and foundation to make it easier to keep data secure. Nothing is completely 
-free -- LunaSec still requires some effort to onboard -- but at least we hope to make it easier than it was before and to
+free -- LunaSec still requires some effort to onboard -- but we hope at least to make it easier than it was before and to
 make it simpler for companies to prioritize security in the future.
 
 In that spirit, here are a few reasons we think LunaSec is unique:
@@ -102,7 +104,7 @@ by Software Developers that aren't experts in security.
 ### We've seen how painful many security tools are to use or migrate to.
 It's easier when you tackle a problem one step at a time. 
 
-That's why LunaSec is [modular](https://www.lunasec.io/docs/pages/overview/security/levels/) so that adoption can be gradual.
+That's why LunaSec is [modular](https://www.lunasec.io/docs/pages/overview/security/levels/), so that its adoption can be gradual.
 
 ### We've seen every company re-invent the wheel time after time.
 That's why LunaSec was made [Open Source](https://github.com/lunasec-io/lunasec/blob/master/LICENSE) under a 
@@ -122,15 +124,15 @@ We're able to provide paid support and enterprise features because LunaSec is a
 [YCombinator](https://www.ycombinator.com/companies/lunasec) and other top Silicon Valley Venture Capital firms.
 
 (Read through our [docs](https://www.lunasec.io/docs/pages/overview/introduction/) for more context about what LunaSec
-does differently)
+does differently.)
 
 ## How to support LunaSec
 If you like what we're doing, and you would like to show your support, we have a few ways that you can help us out:
 
-- Throw us a Star on [Github](https://github.com/lunasec-io/lunasec),
-- Post about us on social media and spread the word by telling your friends,
-- Try out our [example app](https://www.lunasec.io/docs/pages/overview/demo-app/overview/) and [tutorials](https://www.lunasec.io/docs/pages/getting-started/dedicated-tokenizer/introduction/),
-- Deploy LunaSec in your infrastructure ([guide](https://www.lunasec.io/docs/pages/deployment/deploy-with-aws/)),
+- Throw us a Star on [Github](https://github.com/lunasec-io/lunasec)
+- Post about us on social media and spread the word by telling your friends
+- Try out our [example app](https://www.lunasec.io/docs/pages/overview/demo-app/overview/) and [tutorials](https://www.lunasec.io/docs/pages/getting-started/dedicated-tokenizer/introduction/)
+- Deploy LunaSec in your infrastructure ([guide](https://www.lunasec.io/docs/pages/deployment/deploy-with-aws/))
 - [Contact us](https://www.lunasec.io/contact) about our paid services (premium support, custom onboarding, and enterprise features)
 
 Thank you for being a part of Open Source security software with LunaSec!