git: 2a9f06e670 - main - Fix typo in Network servers chapter in the Handbook

From: Sergio Carlavilla Delgado <carlavilla_at_FreeBSD.org>
Date: Wed, 02 Nov 2022 19:42:48 UTC
The branch main has been updated by carlavilla:

URL: https://cgit.FreeBSD.org/doc/commit/?id=2a9f06e670f0f69ce969fc9d65de736b54d45c87

commit 2a9f06e670f0f69ce969fc9d65de736b54d45c87
Author:     ghislain <ghislain@smartix.llc>
AuthorDate: 2022-11-02 19:40:59 +0000
Commit:     Sergio Carlavilla Delgado <carlavilla@FreeBSD.org>
CommitDate: 2022-11-02 19:40:59 +0000

    Fix typo in Network servers chapter in the Handbook
    
    PR:             265247
    Approved by:    carlavilla@
    Reviewed by:    grahamperrin@, pauamma@
---
 documentation/content/en/books/handbook/network-servers/_index.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/documentation/content/en/books/handbook/network-servers/_index.adoc b/documentation/content/en/books/handbook/network-servers/_index.adoc
index 8e63d6c90b..822c49f0d2 100644
--- a/documentation/content/en/books/handbook/network-servers/_index.adoc
+++ b/documentation/content/en/books/handbook/network-servers/_index.adoc
@@ -643,7 +643,7 @@ Think of the NIS domain name as the name for a group of hosts.
 Some organizations choose to use their Internet domain name for their NIS domain name.
 This is not recommended as it can cause confusion when trying to debug network problems.
 The NIS domain name should be unique within the network and it is helpful if it describes the group of machines it represents.
-For example, the Art department at Acme Inc. might be in the "acme-art"NIS domain.
+For example, the Art department at Acme Inc. might be in the "acme-art" NIS domain.
 This example will use the domain name `test-domain`.
 
 However, some non-FreeBSD operating systems require the NIS domain name to be the same as the Internet domain name.
@@ -922,7 +922,7 @@ Since RPC is a broadcast-based service, any system running ypbind within the sam
 To prevent unauthorized transactions, man:ypserv[8] supports a feature called "securenets" which can be used to restrict access to a given set of hosts.
 By default, this information is stored in [.filename]#/var/yp/securenets#, unless man:ypserv[8] is started with `-p` and an alternate path.
 This file contains entries that consist of a network specification and a network mask separated by white space.
-Lines starting with `#` are considered to be comments.
+Lines starting with `+"#"+` are considered to be comments.
 A sample [.filename]#securenets# might look like this:
 
 [.programlisting]
@@ -1058,7 +1058,7 @@ INTERNS (,able,test-domain)     (,baker,test-domain)
 ....
 
 Each entry configures a netgroup. The first column in an entry is the name of the netgroup.
-Each set of brackets represents either a group of one or more users or the name of another netgroup.
+Each set of parentheses represents either a group of one or more users or the name of another netgroup.
 When specifying a user, the three comma-delimited fields inside each group represent:
 
 . The name of the host(s) where the other fields representing the user are valid. If a hostname is not specified, the entry is valid on all hosts.