Merge pull request w3c#3915 from ewilligers/latinreq

ewilligers · web-flow · commit fc5c1304b8a7 · 2019-05-11T13:07:14.000+10:00
[[css-gcpm-4] Fix reference to dpub-latinreq
diff --git a/css-gcpm-4/Overview.bs b/css-gcpm-4/Overview.bs
@@ -36,7 +36,7 @@ The existing mechanisms do not cover many use cases.
 
 Headers often contain document content, and it is desirable to both display that content normally (for example, as an <code>h1</code>) and to use the content in a running head. [[CSS3-REGIONS]] allows for an element to be moved to a ''named flow'', but doesn't allow for using the same content in two ways. The 'copy-into' property allows an element to be copied into a content fragment which can then be placed with the 'content' property.
 
-<p class="note">Use cases for running heads can be found in [[LATINREQ]] http://w3c.github.io/dpub-pagination/#content</p>
+<p class="note">Use cases for running heads can be found in [[dpub-latinreq]] https://w3c.github.io/dpub-pagination/#content</p>
 
 
 

Original file line number	Diff line number	Diff line change
`@@ -36,7 +36,7 @@ The existing mechanisms do not cover many use cases.`
`36`	`36`
`37`	`37`	`Headers often contain document content, and it is desirable to both display that content normally (for example, as an <code>h1</code>) and to use the content in a running head. [[CSS3-REGIONS]] allows for an element to be moved to a ''named flow'', but doesn't allow for using the same content in two ways. The 'copy-into' property allows an element to be copied into a content fragment which can then be placed with the 'content' property.`
`38`	`38`
`39`		`-<p class="note">Use cases for running heads can be found in [[LATINREQ]] http://w3c.github.io/dpub-pagination/#content</p>`
	`39`	`+<p class="note">Use cases for running heads can be found in [[dpub-latinreq]] https://w3c.github.io/dpub-pagination/#content</p>`
`40`	`40`
`41`	`41`
`42`	`42`