-
Notifications
You must be signed in to change notification settings - Fork 1.6k
content: Tidy PWA Lighthouse audit posts #1343
Comments
Comments from @patrickhulce, originally on Lighthouse PR 9539:
|
No updates. |
The scope of this PR is to normalize the content. We'll do a more thorough review of the content in a subsequent PR. |
Status: Normalization is done. Michael is fixing some docs that aren't talking about what the audit is actually measuring. |
Both normalization and quality work complete. Ready for @kaycebasques to review. Note: I didn't add content where it might be helpful because I didn't want to step out of scope, but there are some posts that are very slim. Most immediately, |
@kaycebasques to do a tech writer review, there's an open question around heading wording. Look at redirects post and redirects HTTPS posts. These were re-written. Michael did quality fixes too FYI Rob checked consistency of normalization, skimmed content, mostly looking for normalization stuff |
Done! Woohoo! Off to @robdodson to publish. |
@kaycebasques, you introduced a title error when you committed your changes. See PR for details. |
Thanks @mfriesenhahn for fixing my goof, off to @robdodson to publish |
it's uuuuuup |
@kaycebasques, remember to send the feedback survey! |
Author: @mfriesenhahn
Reviewer: @kaycebasques
Target publish date:
Check this box if this is a hard deadline.
Check this box if you'd like your reviewer to fix grammar and punctuation issues for you.
Process
Check out the web.dev writing process.
When you're ready, make a copy of this template
and fill in the proposal and outline sections. When you're finished, drop a link
to the doc in the 1st step below and check the box. A member of the web.dev team
will assign this ticket to themselves and work as your reviewer to help you
complete the remaining steps.
The text was updated successfully, but these errors were encountered: