diff --git a/winsup/cygwin/how-cygheap-works.txt b/winsup/cygwin/how-cygheap-works.txt
index 49542871c..ab4131d2b 100644
--- a/winsup/cygwin/how-cygheap-works.txt
+++ b/winsup/cygwin/how-cygheap-works.txt
@@ -1,4 +1,4 @@
-Copyright 2001 Christopher Faylor
+Copyright 2001 Red Hat Inc., Christopher Faylor
 
 Cygwin has recently adopted something called the "cygwin heap".  This is
 an internal heap that is inherited by forked/execed children.  It
diff --git a/winsup/cygwin/how-signals-work.txt b/winsup/cygwin/how-signals-work.txt
index cf4915494..aaaea448a 100644
--- a/winsup/cygwin/how-signals-work.txt
+++ b/winsup/cygwin/how-signals-work.txt
@@ -1,3 +1,5 @@
+Copyright 2001 Red Hat Inc., Christopher Faylor
+
 [This is not yet complete. -cgf]
 
 How do signals work?
diff --git a/winsup/cygwin/how-vfork-works.txt b/winsup/cygwin/how-vfork-works.txt
index 888f4f6b5..c45228cad 100644
--- a/winsup/cygwin/how-vfork-works.txt
+++ b/winsup/cygwin/how-vfork-works.txt
@@ -1,3 +1,5 @@
+Copyright 2001 Red Hat Inc., Christopher Faylor
+
 How does vfork work?
 
 When a program calls vfork, cygwin attempts to short circuit its