Commit0f85db9

committed

docs: use consistent markup for PostgreSQL

"PostgreSQL" should use <productname> markup consistenktly, so thatif we do apply styling on it it will be consistently applied. Fixby renaming the one exception to the rule.Discussion:https://postgr.es/m/F2EF5217-27A3-4962-9AE5-2E6C2CB3D0FF@yesql.se

1 parent106f26a commit0f85db9Copy full SHA for 0f85db9

File tree

-1

lines changed

-1

lines changed

Lines changed: 1 addition & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -2672,7 +2672,7 @@ TIMESTAMP WITH TIME ZONE '2004-10-19 10:23:54+02'`
`2672`	`2672`	`To complicate matters, some jurisdictions have used the same timezone`
`2673`	`2673`	`abbreviation to mean different UTC offsets at different times; for`
`2674`	`2674`	`example, in Moscow <literal>MSK</literal> has meant UTC+3 in some years and`
`2675`		`- UTC+4 in others. <application>PostgreSQL</application> interprets such`
	`2675`	`+ UTC+4 in others. <productname>PostgreSQL</productname> interprets such`
`2676`	`2676`	`abbreviations according to whatever they meant (or had most recently`
`2677`	`2677`	`meant) on the specified date; but, as with the <literal>EST</literal> example`
`2678`	`2678`	`above, this is not necessarily the same as local civil time on that date.`

Comments

(0)