Commitab35b08

Thomas G. Lockhart

committed

Expunge "UNIX" in favor of "Unix".

A few other changes, but I forget what :(

1 parentd0741fb commitab35b08Copy full SHA for ab35b08

File tree

+399

-374

lines changed

+399

-374

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -282,7 +282,7 @@ SELECT name, population`
`282`	`282`
`283`	`283`	`<note>`
`284`	`284`	`<para>`
`285`		`- OnUNIX systems, this is always midnight, January 1, 1970 GMT.`
	`285`	`+ OnUnix systems, this is always midnight, January 1, 1970 GMT.`
`286`	`286`	`</para>`
`287`	`287`	`</note>`
`288`	`288`	`</para>`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -174,7 +174,7 @@`
`174`	`174`	`<para>`
`175`	`175`	`The <firstterm>parser</firstterm> defined in`
`176`	`176`	`<filename>gram.y</filename> and <filename>scan.l</filename> is`
`177`		`- built using theUNIX tools <application>yacc</application>`
	`177`	`+ built using theUnix tools <application>yacc</application>`
`178`	`178`	`and <application>lex</application>.`
`179`	`179`	`</para>`
`180`	`180`	`</listitem>`
`@@ -194,7 +194,7 @@`
`194`	`194`	`The parser has to check the query string (which arrives as`
`195`	`195`	`plain ASCII text) for valid syntax. If the syntax is correct a`
`196`	`196`	`<firstterm>parse tree</firstterm> is built up and handed back otherwise an error is`
`197`		`- returned. For the implementation the well knownUNIX`
	`197`	`+ returned. For the implementation the well knownUnix`
`198`	`198`	`tools <application>lex</application> and <application>yacc</application>`
`199`	`199`	`are used.`
`200`	`200`	`</para>`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,7 @@`
`11`	`11`	`somewhat clearer.`
`12`	`12`	`In database jargon, <ProductName>Postgres</ProductName> uses a simple "process`
`13`	`13`	`per-user" client/server model. A <ProductName>Postgres</ProductName> session`
`14`		`- consists of the following cooperatingUNIX processes (programs):`
	`14`	`+ consists of the following cooperatingUnix processes (programs):`
`15`	`15`
`16`	`16`	`<ItemizedList>`
`17`	`17`	`<ListItem>`
`@@ -75,7 +75,7 @@ Note that the <ProductName>Postgres</ProductName> superuser does not`
`75`	`75`	`have to be a special user (e.g., a user named`
`76`	`76`	`"postgres"), although many systems are installed that way.`
`77`	`77`	`Furthermore, the <ProductName>Postgres</ProductName> superuser should`
`78`		`- definitely not be theUNIX superuser, "root"! In any`
	`78`	`+ definitely not be theUnix superuser, "root"! In any`
`79`	`79`	`case, all files relating to a database should belong to`
`80`	`80`	`this <ProductName>Postgres</ProductName> superuser.`
`81`	`81`	`</Para>`

Lines changed: 2 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -11,7 +11,7 @@`
`11`	`11`	`somewhat clearer.`
`12`	`12`	`In database jargon, <ProductName>Postgres</ProductName> uses a simple "process`
`13`	`13`	`per-user" client/server model. A <ProductName>Postgres</ProductName> session`
`14`		`- consists of the following cooperatingUNIX processes (programs):`
	`14`	`+ consists of the following cooperatingUnix processes (programs):`
`15`	`15`	`</Para>`
`16`	`16`
`17`	`17`	`<ItemizedList>`
`@@ -80,7 +80,7 @@`
`80`	`80`	`have to be a special user (e.g., a user named`
`81`	`81`	`"postgres"). Furthermore, the <ProductName>Postgres</ProductName> superuser`
`82`	`82`	`should`
`83`		`- definitely not be theUNIX superuser ("root")! In any`
	`83`	`+ definitely not be theUnix superuser ("root")! In any`
`84`	`84`	`case, all files relating to a database should belong to`
`85`	`85`	`this <ProductName>Postgres</ProductName> superuser.`
`86`	`86`	`</Para>`

Comments

(0)