diff --git a/doc/bird.sgml b/doc/bird.sgml
index a0b45f49..014225d1 100644
--- a/doc/bird.sgml
+++ b/doc/bird.sgml
@@ -195,7 +195,7 @@ privileges (capabilities CAP_NET_*). Note that the control socket is created
 before the privileges are dropped, but the config file is read after that. The
 privilege restriction is not implemented in BSD port of BIRD.
 
-<p>A nonprivileged user (as an argument to <cf/-u/ options) may be the user
+<p>An unprivileged user (as an argument to <cf/-u/ options) may be the user
 <cf/nobody/, but it is suggested to use a new dedicated user account (like
 <cf/bird/). The similar considerations apply for the group option, but there is
 one more condition -- the users in the same group can use <file/birdc/ to
@@ -288,7 +288,7 @@ extensive way.
 a comment, whitespace characters are treated as a single space. If there's a
 variable number of options, they are grouped using the <cf/{ }/ brackets. Each
 option is terminated by a <cf/;/. Configuration is case sensitive. There are two
-ways how to name symbols (like protocol names, filter names, constats etc.). You
+ways how to name symbols (like protocol names, filter names, constants etc.). You
 can either use a simple string starting with a letter followed by any
 combination of letters and numbers (e.g. "R123", "myfilter", "bgp5") or you can
 enclose the name into apostrophes (<cf/'/) and than you can use any combination
@@ -835,7 +835,7 @@ This argument can be omitted if there exists only a single instance.
 	configuration could be either confirmed using <cf/configure confirm/
 	command, or it will be reverted to the old one when the config timer
 	expires. This is useful for cases when reconfiguration breaks current
-	routing and a router becames inaccessible for an administrator. The
+	routing and a router becomes inaccessible for an administrator. The
 	config timeout expiration is equivalent to <cf/configure undo/
 	command. The timeout duration could be specified, default is 300 s.
 
@@ -1016,7 +1016,7 @@ foot).
 	of type <cf/string/, print such variables, use standard string
 	comparison operations (e.g. <cf/=, !=, &lt;, &gt;, &lt;=, &gt;=/), but
 	you can't concatenate two strings. String literals are written as
-	<cf/"This is a string constant"/. Additionaly matching <cf/&tilde;/
+	<cf/"This is a string constant"/. Additionally matching <cf/&tilde;/
 	operator could be used to match a string value against a shell pattern
 	(represented also as a string).
 
@@ -1579,7 +1579,7 @@ protocol bfd [&lt;name&gt;] {
 
 	The session is identified by the IP address of the neighbor, with
 	optional specification of used interface and local IP. By default
-	the neighbor must be directly connected, unless the the session is
+	the neighbor must be directly connected, unless the session is
 	configured as multihop. Note that local IP must be specified for
 	multihop sessions.
 </descrip>
@@ -1622,7 +1622,7 @@ protocol bfd [&lt;name&gt;] {
 	Default: 5.
 
 	<tag>passive <m/switch/</tag>
-	Generally, both BFD session endpoinds try to establish the session by
+	Generally, both BFD session endpoints try to establish the session by
 	sending control packets to the other side. This option allows to enable
 	passive mode, which means that the router does not send BFD packets
 	until it has received one from the other side. Default: disabled.
@@ -2758,7 +2758,7 @@ protocol ospf &lt;name&gt; {
 	<tag>dead <M>num</M></tag>
 	When the router does not receive any messages from a neighbor in
 	<m/dead/ seconds, it will consider the neighbor down. If both directives
-	<cf/dead count/ and <cf/dead/ are used, <cf/dead/ has precendence.
+	<cf/dead count/ and <cf/dead/ are used, <cf/dead/ has precedence.
 
 	<tag>secondary <M>switch</M></tag>
 	On BSD systems, older versions of BIRD supported OSPFv2 only for the