minor edits

Author: gregsdennis

Diff for: _posts/2024/2024-06-20-joining-net-foundation.md

@@ -12,13 +12,13 @@ That's right!  The `json-everything` project is officially a .Net Foundation mem
 
 ### Inspiration from JSON Schema
 
-A couple years ago JSON Schema started the onboarding process to join the OpenJS Foundation.  Joining a foundation in general means that they can lean on the experience of other members for help on things like governance, outreach, project organization, etc.  It helps to have the backing of a larger organization.
+A couple years ago JSON Schema started the onboarding process to join the OpenJS Foundation.  Joining a foundation means that they can lean on the experience of other members for help on things like governance, outreach, project organization, etc.  It helps to have the backing of a larger organization.
 
 However, while the specification group would be joining the Foundation, all of the tooling built around the spec remained independent.
 
 Sadly, the OpenJS Foundation onboarding journey was interrupted, so JSON Schema is still independent.  We'll likely try again, maybe with another foundation, but that's on the horizon for right now... and this post is about `json-everything` anyway!
 
-### A push through JSON Path
+### A push via JSON Path
 
 As part of the JSON Path specification effort with IETF, I reached out to a lot of JSON Path implementations to let them know a specification was coming, and I kept my eyes open for other places where JSON Path was being used and/or requested.  One of those places was a [.Net issue](https://github.com/dotnet/runtime/issues/31068) requesting that _System.Text.Json_ get first-party support for the query syntax.  I posted about _JsonPath.Net_, and [one of the responses](https://github.com/dotnet/runtime/issues/31068#issuecomment-1992390964) intrigued me.
 
@@ -32,11 +32,11 @@ As I created these libraries to help developers make great software, this barrie
 
 ### Investigation
 
-Looking into the three options mentioned, I first discovered that I'm not Microsoft.  (This was a devastating realization, and I had to re-evaluate my entire worldview.)  I'm also not a .Net Foundation member, but I could look into joining.  But first I wondered what it would take to have my packages verified on Nuget.
+Looking into the three options mentioned, I first discovered that I am not Microsoft.  (This was a devastating realization, and I had to re-evaluate my entire worldview.)  I'm also not a .Net Foundation member, but I could look into joining.  But first I wondered what it would take to have my packages verified on Nuget.
 
 Verifying packages is pretty simple: you just need a signing certificate.   There are a [_lot_ of companies](https://www.google.com/search?q=signing+certificate) that provide them... and WOW are they expensive!
 
-So, .Net Foundation seemed to be my best option.  I researched the [benefits](https://dotnetfoundation.org/membership/participation-types), the requirements, and the T&Cs.  (I'm looking for links to all of the pages I found before, but the site has changed, and it looks like the application process now starts by filling out a web form.  When I looked into it before, I just had to [open an issue](https://github.com/dotnet-foundation/projects/issues/new?assignees=sbwalker%2CChrisSfanos&labels=project+application%2Cproject+support&projects=&template=application.yml&title=Issue%3A+New+.NET+Foundation+Project+Application) on the .Net Foundation's Projects repo.  You should probably go through the web form if you want to join.)
+So, .Net Foundation seemed to be my best option.  I researched the [benefits](https://dotnetfoundation.org/membership/participation-types), the requirements, and the T&Cs.  (I'm looking for links to all of the pages I found before, but the site has changed, and it looks like the application process now starts by filling out a web form.  When I looked into it before, I just had to [open an issue](https://github.com/dotnet-foundation/projects/issues/new?assignees=sbwalker%2CChrisSfanos&labels=project+application%2Cproject+support&projects=&template=application.yml&title=Issue%3A+New+.NET+Foundation+Project+Application) on the .Net Foundation's Projects repo.  If you'd like to join, I recommend going through the web form.)
 
 ### Application
 
@@ -52,13 +52,13 @@ I was quite pleased when I received notification that my humble `json-everything
 
 ## How it's going
 
-I'm currently still in the onboarding process.  There a [checklist](https://github.com/dotnet-foundation/projects/issues/367#issuecomment-2155296470) on my application issue that details all of the things that need to happen (or ensure have happened).
+I'm currently finishing up the onboarding process.  There a [checklist](https://github.com/dotnet-foundation/projects/issues/367#issuecomment-2155296470) on my application issue that details all of the things that need to happen (or ensure have happened).
 
 I think the biggest change is that the project will be under a [CLA](https://dotnetfoundation.org/docs/default-source/default-document-library/contribution-license-agreement.pdf).  I've read through it, and it basically says the contributor allows the project and .Net Foundation to distribute and potentially patent their contribution (as part of the project).  I'm not sure anything contributed to `json-everything` will or could be patented, but I suppose it's come up enough for them to add it to the CLA.  Outside of that, the contributor retains all rights.
 
 I've also moved all of the related repos into a new `json-everything` org, and I spruced up the place a bit, made all the readmes pretty.  GitHub has done a good job of applying redirects, so everyone's links should still work.
 
-Then there are some housekeeping things for the repo and public announcement stuff, which... I expect I should probably wait for that before publishing this...
+Then there are some housekeeping things for the repos and their public announcement, which will come via their newsletter.
 
 ## The future