From 4bcae730396fa07b95edbed5a4d950994375b434 Mon Sep 17 00:00:00 2001
From: npm1 <npm@chromium.org>
Date: Thu, 27 Feb 2020 14:44:21 -0500
Subject: [PATCH] Fix Note about supportedEntryTypes

Fixes https://github.com/w3c/paint-timing/issues/48. The type introduced in this spec is just 'paint'.
---
 painttiming.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/painttiming.bs b/painttiming.bs
index ac4386a..669afee 100644
--- a/painttiming.bs
+++ b/painttiming.bs
@@ -83,7 +83,7 @@ The {{PerformancePaintTiming}} interface {#sec-PerformancePaintTiming}
 * The {{PerformanceEntry/startTime}} attribute must return a {{DOMHighResTimeStamp}} of when the paint occured.
 * The {{PerformanceEntry/duration}} attribute must return 0.
 
-NOTE: A user agent implementing {{PerformancePaintTiming}} would need to include <code>"first-paint"</code> and <code>"first-contentful-paint"</code> in {{PerformanceObserver/supportedEntryTypes}} for {{Window}} contexts.
+NOTE: A user agent implementing {{PerformancePaintTiming}} would need to include <code>"paint"</code> in {{PerformanceObserver/supportedEntryTypes}} for {{Window}} contexts.
 This allows developers to detect support for paint timing.
 
 Processing model {#sec-processing-model}