Fix version numbers in FAQs

* Use architecture-agnostic URLs.
* Make FAQ 10.18 less dramatic and less condescending.

PR:                     261816
Patch by:               pauamma@
Reviewd by:             grahamperrin@
Differential Revision:  https://reviews.freebsd.org/D35345

1 files changed, 11 insertions, 13 deletions

diff --git a/documentation/content/en/books/faq/_index.adoc b/documentation/content/en/books/faq/_index.adoc
index b56a880137..de3500ff6e 100644
--- a/documentation/content/en/books/faq/_index.adoc
+++ b/documentation/content/en/books/faq/_index.adoc
@@ -2,7 +2,7 @@
 title: Frequently Asked Questions for FreeBSD 12.X and 13.X
 authors: 
   - author: The FreeBSD Documentation Project
-copyright: 1995-2021 The FreeBSD Documentation Project
+copyright: 1995-2022 The FreeBSD Documentation Project
 description: Frequently Asked Questions, and answers, covering all aspects of FreeBSD
 trademarks: ["freebsd", "ibm", "ieee", "adobe", "intel", "linux", "microsoft", "opengroup", "sun", "netbsd", "general"] 
 bookOrder: 5
@@ -191,8 +191,8 @@ _FreeBSD-CURRENT_, on the other hand, has been one unbroken line since 2.0 was r
 For more detailed information on branches see "extref:{releng}[FreeBSD Release Engineering: Creating the Release Branch, rel-branch]",
 the status of the branches and the upcoming release schedule can be found on the https://www.FreeBSD.org/releng[Release Engineering Information] page.
 
-Version https://download.FreeBSD.org/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}] is the latest release from the {rel-stable} branch; it was released in {rel121-current-date}.
-Version https://download.FreeBSD.org/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}] is the latest release from the {rel2-stable} branch; it was released in {rel113-current-date}.
+Version {u-rel123-announce}[{rel123-current}] is the latest release from the {rel2-stable} branch; it was released on {rel123-current-date}.
+Version {u-rel131-announce}[{rel131-current}] is the latest release from the {rel-stable} branch; it was released on {rel131-current-date}.
 
 [[release-freq]]
 === When are FreeBSD releases made?
@@ -237,11 +237,11 @@ and there are no restrictions on who may take part in the discussion.
 [[where-get]]
 === Where can I get FreeBSD?
 
-Every significant release of FreeBSD is available via anonymous FTP from the https://download.FreeBSD.org/releases/[FreeBSD FTP site]:
+Every supported release of FreeBSD is available from the https://www.freebsd.org/where/[FreeBSD release locator page]:
 
-* The latest {rel-stable} release, {rel121-current}-RELEASE can be found in the https://download.FreeBSD.org/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}-RELEASE directory].
-* link:https://www.FreeBSD.org/snapshots/[Snapshot] releases are made monthly for the <<current,-CURRENT>> and <<stable,-STABLE>> branch, these being of service purely to bleeding-edge testers and developers.
-* The latest {rel2-stable} release, {rel113-current}-RELEASE can be found in the https://download.FreeBSD.org/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}-RELEASE directory].
+* For the latest {rel-stable} release, {rel131-current}-RELEASE, follow the link for link:https://www.freebsd.org/where/#download-rel131[the appropriate architecture and installation mode for {rel131-current}-RELEASE].
+* For the latest {rel2-stable} release, {rel123-current}-RELEASE, follow the link for link:https://www.freebsd.org/where/#download-rel123[the appropriate architecture and installation mode for {rel123-current}-RELEASE].
+* link:https://www.FreeBSD.org/snapshots/[Snapshot] releases are made monthly for the <<current,-CURRENT>> and <<stable,-STABLE>> branches, these being of service purely to bleeding-edge testers and developers.
 
 Information about obtaining FreeBSD on CD, DVD, and other media can be found in extref:{handbook}[the Handbook, mirrors].
 
@@ -574,7 +574,7 @@ bsdconfig provides a nice interface to configure FreeBSD post-installation.
 ==== I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best?
 
 This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly.
-Read through the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}] and search the mailing list https://www.FreeBSD.org/search/#mailinglists[archives] before asking about the latest and greatest hardware.
+Read through the Hardware Notes for FreeBSD link:{u-rel123-hardware}[{rel123-current}] or link:{u-rel131-hardware}[{rel131-current}] and search the https://www.FreeBSD.org/search/#mailinglists[mailing list archives] before asking about the latest and greatest hardware.
 Chances are a discussion about that type of hardware took place just last week.
 
 Before purchasing a laptop, check the archives for {freebsd-questions},
@@ -663,7 +663,7 @@ to [.filename]#/etc/rc.conf#
 [[supported-peripherals]]
 ==== What kind of peripherals does FreeBSD support?
 
-See the complete list in the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}].
+See a list of hardware known to work and any applicable restrictions in the Hardware Notes for FreeBSD link:{u-rel123-hardware}[{rel123-current}] or link:{u-rel131-hardware}[{rel131-current}].
 
 [[compatibility-kbd-mice]]
 === Keyboards and Mice
@@ -1905,13 +1905,11 @@ See the man:init[8] manual page for details on `securelevel`, and see [.filename
 === Why is rpc.statd using 256 MB of memory?
 
 No, there is no memory leak, and it is not using 256 MB of memory.
-For convenience, `rpc.statd` maps an obscene amount of memory into its address space.
+For convenience, `rpc.statd` maps a large amount of memory into its address space.
 There is nothing terribly wrong with this from a technical standpoint; it just throws off things like man:top[1] and man:ps[1].
 
-man:rpc.statd[8] maps its status file (resident on [.filename]#/var#) into its address space;
+man:rpc.statd[8] maps its status file ([.filename]#/var/db/statd.status#) into its address space;
 to save worrying about remapping the status file later when it needs to grow, it maps the status file with a generous size.
-This is very evident from the source code, where one can see that the length argument to man:mmap[2] is `0x10000000`,
-or one sixteenth of the address space on an IA32, or exactly 256 MB.
 
 [[unsetting-schg]]
 === Why can I not unset the schg file flag?