chore: pr feedback

Author: 43081j

rfcs/NNNN-postcss-lit-adoption.md

@@ -6,35 +6,35 @@ PR: #17
 
 # Official postcss/tailwind support
 
-As part of unifying the standard tools around lit, it would make sense to move
+As part of unifying the standard tools around Lit, it would make sense to move
 the [postcss-lit](https://github.com/43081j/postcss-lit) project into the
-lit monorepo as an official solution to inline CSS transforms (e.g. tailwind).
+Lit monorepo as an official solution to inline CSS transforms (e.g. tailwind).
 
 ## Objective
 
 A strategy for how we will move the project into the monorepo.
 
 ### Goals
-- Moving the postcss-lit project into the lit monorepo
+- Moving the postcss-lit project into the Lit monorepo
 - Potentially documenting the project in an appropriate place (or a blog post)
 
 ### Non-Goals
 - Transfer of responsibility (it is expected I will continue being the primary
-maintainer to avoid extra burden on the lit team)
+maintainer to avoid extra burden on the Lit team)
 
 ## Motivation
 
 The project already functions well and has high usage, but could benefit hugely
 in terms of discovery and support by being in the monorepo.
 
-- **Discovery:** we are regularly asked by users how to integrate lit with
+- **Discovery:** we are regularly asked by users how to integrate Lit with
 tailwind and other such CSS solutions. Having an officially supported and
 maintained integration will make this clearer
 - **Support:** we are more likely to receive community contributions through
 issues and pull requests
 
 It will also become much easier to keep the integration in sync with the
-most current version of lit, as we are likely to update it in line with
+most current version of Lit, as we are likely to update it in line with
 any breaking changes elsewhere in the monorepo.
 
 ## Detailed Design
@@ -78,16 +78,13 @@ N/A
 
 ### Documentation Plan
 
-We should create blog posts explaining the two ways users can transform
+We should create articles explaining the two ways users can transform
 CSS:
 
 - Inline CSS via postcss-lit
 - External CSS via rollup plugins (using CSS imports)
 
-These could be linked in the lit website.
-
-Alternatively, we could document both solutions in the lit website entirely
-rather than blog posts.
+These could be linked in the Lit website.
 
 ## Downsides