remove outdated comments

Author: lubieowoce

packages/next/src/server/app-render/app-render.tsx

@@ -301,7 +301,6 @@ function parseRequestHeaders(
   headers: IncomingHttpHeaders,
   options: ParseRequestHeadersOptions
 ): ParsedRequestHeaders {
-  // dev warmup requests are treated as prefetch RSC requests
   // runtime prefetch requests are *not* treated as prefetch requests
   // (TODO: this is confusing, we should refactor this to express this better)
   const isPrefetchRequest = headers[NEXT_ROUTER_PREFETCH_HEADER] === '1'
@@ -310,7 +309,6 @@ function parseRequestHeaders(
 
   const isHmrRefresh = headers[NEXT_HMR_REFRESH_HEADER] !== undefined
 
-  // dev warmup requests are treated as prefetch RSC requests
   const isRSCRequest = headers[RSC_HEADER] !== undefined
 
   const shouldProvideFlightRouterState =

packages/next/src/server/lib/patch-fetch.ts

@@ -283,7 +283,6 @@ export function createPatchedFetcher(
     const workStore = workAsyncStorage.getStore()
     const workUnitStore = workUnitAsyncStorage.getStore()
 
-    // During static generation we track cache reads so we can reason about when they fill
     let cacheSignal = workUnitStore ? getCacheSignal(workUnitStore) : null
     if (cacheSignal) {
       cacheSignal.beginRead()

test/development/app-dir/cache-components-dev-warmup/app/simple/page.tsx

@@ -12,13 +12,6 @@ export default async function Page() {
   return (
     <main>
       <h1>Warmup Dev Renders</h1>
-      <p>
-        In Dev when cacheComponents is enabled requests are preceded by a cache
-        warming prerender. Without PPR this prerender only includes up to the
-        nearest Loading boundary (loading.tsx) and will never include the Page
-        itself. When PPR is enabled it will include everything that is
-        prerenderable including the page if appropriate.
-      </p>
 
       <CachedData label="page" cacheKey={CACHE_KEY} />
       <SuccessiveCachedData label="page" cacheKey={CACHE_KEY} />