Original text:
due to a problem with the name server."  (Quoted from RFC1035, Section 4.1.1.) <del> "Name Error - Meaningful only for responses from an authoritative name server, this code signifies that the domain name referenced </del>  in the query does not exist."  (Quoted from RFC1035, Section 4.1.1.)  RFC2308 established NXDOMAIN as a synonym for Name Error. A program "that extract[s] information from name servers in response to client requests."  (Quoted from RFC1034, Section 2.4) <del> "The resolver is located on the same machine as the program that requests the resolver's services, but it may need to consult name servers on other hosts."  (Quoted from RFC1034, Section 5.1) A resolver performs queries for a name, type, and class, and </del>  receives answers.  The logical function is called "resolution". In practice, the term is usually referring to some specific type of resolver (some of which are defined below), and understanding requests for recursion.  It will "not normally generate any queries of its own.  Instead, it answers non-recursive queries from iterative resolvers looking for information in zones it <del> serves."  (Quoted from RFC4697, Section 2.4) </del>  The act of a client requesting a copy of a zone and an authoritative server sending the needed information.  (See zones resolver being informed. A full-service resolver that accepts and processes queries from <del> any (or nearly any) stub resolver.  This is sometimes also called a "public resolver", although the term "public resolver" is used </del>  more with open resolvers that are meant to be open, as compared to the vast majority of open resolvers that are probably misconfigured to be open.  Open resolvers are discussed in the delegation, even though they are not themselves authoritative data.  "A lame delegations exists when a nameserver is delegated responsibility for providing nameservice for a zone (via NS records) but is not performing nameservice for that zone (usually Like the NSEC record, the NSEC3 record also provides authenticated denial of existence; however, NSEC3 records mitigate against zone <del> enumeration and support Opt-Out.  NSEC resource records require </del>  associated NSEC3PARAM resource records.  NSEC3 and NSEC3PARAM resource records are defined in RFC5155.

Reviewer comments:
There is one typo at "Authoritative data:". Other differences are OK. | , Section 2, defines "Authoritative RRset" which is related | to authoritative data [bu] has a more precise definition. ("bu"is "but" ?)
I missed to change branch and I commited to this branch. please review "f172affe0f5d111af23f8c48f9ed5715e7b314d0".

Revised text:
due to a problem with the name server."  (Quoted from RFC1035, Section 4.1.1.)  <ins> "Name Error - This code signifies that the domain name referenced </ins> in the query does not exist."  (Quoted from RFC1035, Section 4.1.1.)  RFC2308 established NXDOMAIN as a synonym for Name Error. A program "that extract[s] information from name servers in response to client requests."  (Quoted from RFC1034, Section 2.4)  <ins> A resolver performs queries for a name, type, and class, and </ins> receives answers.  The logical function is called "resolution". In practice, the term is usually referring to some specific type of resolver (some of which are defined below), and understanding requests for recursion.  It will "not normally generate any queries of its own.  Instead, it answers non-recursive queries from iterative resolvers looking for information in zones it  <ins> serves."  (Quoted from RFC4697, Section 2.4) In this case, "ignores requests for recursion" means "responds to requests for recursion with responses indicating that recursion was not performed". </ins> The act of a client requesting a copy of a zone and an authoritative server sending the needed information.  (See zones resolver being informed. A full-service resolver that accepts and processes queries from  <ins> any (or nearly any) client.  This is sometimes also called a "public resolver", although the term "public resolver" is used </ins> more with open resolvers that are meant to be open, as compared to the vast majority of open resolvers that are probably misconfigured to be open.  Open resolvers are discussed in the delegation, even though they are not themselves authoritative data. <ins> RFC4033, Section 2, defines "Authoritative RRset" which is related to authoritative data but has a more precise definition. </ins> "A lame delegations exists when a nameserver is delegated responsibility for providing nameservice for a zone (via NS records) but is not performing nameservice for that zone (usually Like the NSEC record, the NSEC3 record also provides authenticated denial of existence; however, NSEC3 records mitigate against zone  <ins> enumeration and support Opt-Out.  NSEC3 resource records require </ins> associated NSEC3PARAM resource records.  NSEC3 and NSEC3PARAM resource records are defined in RFC5155.