third 5 F's (#158)

explanation/networking/configuring-networks.md

@@ -271,7 +271,7 @@ network:
           addresses: [1.1.1.1, 8.8.8.8, 4.4.4.4]
 ```
 
-If you try to ping a host with the name `server1`, your system will automatically query DNS for its Fully Qualified Domain Name (FQDN) in the following order:
+If you try to ping a host with the name `server1`, your system will automatically query DNS for its {term}`Fully Qualified Domain Name (FQDN) <FQDN>` in the following order:
 
 1.  `server1.example.com`
 

explanation/web-services/about-web-servers.md

@@ -7,7 +7,7 @@ Clients, mostly via **web browsers**, request specific resources and the server
 
 ## URLs
 
-Users enter a Uniform Resource Locator (URL) to point to a web server by means of its Fully Qualified Domain Name (FQDN) and a path to the required resource. For example, to view the home page of the [Ubuntu Web site](https://www.ubuntu.com) a user will enter only the FQDN:
+Users enter a Uniform Resource Locator (URL) to point to a web server by means of its {term}`Fully Qualified Domain Name (FQDN) <FQDN>` and a path to the required resource. For example, to view the home page of the [Ubuntu Web site](https://www.ubuntu.com) a user will enter only the FQDN:
 
 ```text
 www.ubuntu.com

how-to/active-directory/join-a-simple-domain-with-the-rid-backend.md

@@ -41,7 +41,7 @@ Right after saving `/etc/samba/smb.conf`, it's always good practice to run the `
     (...)
 
 
-During the domain join process, the tooling will attempt to update the {term}`DNS` server with the hostname of this system. Since its IP is likely not yet registered in DNS, that's kind of a chicken and egg problem. It helps to, beforehand, set the hostname manually to the FQDN. For this example, we will use a host named `n1` in the `example.internal` domain:
+During the domain join process, the tooling will attempt to update the {term}`DNS` server with the hostname of this system. Since its IP is likely not yet registered in DNS, that's kind of a chicken and egg problem. It helps to, beforehand, set the hostname manually to the {term}`FQDN`. For this example, we will use a host named `n1` in the `example.internal` domain:
 
     sudo hostnamectl hostname n1.example.internal
 

how-to/graphics/gpu-virtualization-with-qemu-kvm.md

@@ -3,7 +3,7 @@
 
 ## Graphics
 
-Graphics for QEMU/KVM always comes in two pieces: a front end and a back end.
+Graphics for QEMU/KVM always comes in two pieces: a {term}`frontend` and a backend.
 
 - `frontend`: Controlled via the `-vga` argument, which is provided to the guest. Usually one of `cirrus`, `std`, `qxl`, or `virtio`. The default these days is `qxl` which strikes a good balance between guest compatibility and performance. The guest needs a driver for whichever option is selected -- this is the most common reason to not use the default (e.g., on very old Windows versions).
 

how-to/networking/dpdk-with-open-vswitch.md

@@ -87,7 +87,7 @@ You can check if your issues is known on:
   - [DPDK Mailing Lists](http://dpdk.org/ml)
   - For OpenVswitch-DPDK [OpenStack Mailing Lists](http://openvswitch.org/mlists)
   - Known issues in [DPDK Launchpad Area](https://bugs.launchpad.net/ubuntu/+source/dpdk)
-  - Join the IRC channels \#DPDK or \#openvswitch on freenode.
+  - Join the IRC channels \#DPDK or \#openvswitch on {term}`freenode`.
 
 Issues are often due to missing small details in the general setup. Later on, these missing details cause problems which can be hard to track down to their root cause. 
 

how-to/networking/install-dns.md

@@ -2,7 +2,7 @@
 # Domain Name Service (DNS)
 
 
-Domain Name Service (DNS) is an Internet service that maps IP addresses and fully qualified domain names (FQDN) to one another. In this way, DNS alleviates the need to remember IP addresses. Computers that run DNS are called **name servers**. Ubuntu ships with the Berkley Internet Naming Daemon (BIND), the most common program used for maintaining a name server on Linux.
+Domain Name Service (DNS) is an Internet service that maps IP addresses and {term}`fully qualified domain names (FQDN) <FQDN>` to one another. In this way, DNS alleviates the need to remember IP addresses. Computers that run DNS are called **name servers**. Ubuntu ships with the Berkley Internet Naming Daemon (BIND), the most common program used for maintaining a name server on Linux.
 
 ## Install DNS
 

how-to/openldap/access-control.md

@@ -6,7 +6,7 @@ The management of what type of access (read, write, etc) users should be granted
 
 When we {ref}`installed the slapd package <install-openldap>`, various ACLs were set up automatically. We will look at a few important consequences of those defaults and, in so doing, we'll get an idea of how ACLs work and how they're configured.
 
-To get the effective ACL for an LDAP query we need to look at the ACL entries of both the database being queried, and those of the special frontend database instance. Note that the ACLs belonging to the frontend database are always appended to the database-specific ACLs, and the first match 'wins'.
+To get the effective ACL for an LDAP query we need to look at the ACL entries of both the database being queried, and those of the special {term}`frontend` database instance. Note that the ACLs belonging to the frontend database are always appended to the database-specific ACLs, and the first match 'wins'.
 
 ## Getting the ACLs
 

how-to/openldap/install-openldap.md

@@ -79,7 +79,7 @@ Where the entries mean the following:
 - **`cn={1}cosine,cn=schema,cn=config`**: The Cosine schema
 - **`cn={2}nis,cn=schema,cn=config`**: The Network Information Services (NIS) schema
 - **`cn={3}inetorgperson,cn=schema,cn=config`**: The InetOrgPerson schema
-- **`olcDatabase={-1}frontend,cn=config`**: Frontend database, default settings for other databases
+- **`olcDatabase={-1}frontend,cn=config`**: {term}`Frontend` database, default settings for other databases
 - **`olcDatabase={0}config,cn=config`**: `slapd` configuration database (`cn=config`)
 - **`olcDatabase={1}mdb,cn=config`**: Your database instance (`dc=example,dc=com`)
 

how-to/samba/member-server-in-an-ad-domain.md

@@ -20,7 +20,7 @@ First, let's install the necessary packages:
 sudo apt install realmd samba
 ```
 
-In order to have the joined machine registered in the AD {term}`DNS`, it needs to have an FQDN set. You might have that already, if running the `hostname -f` command returns a full hostname with domain. If it doesn't, then set the hostname as follows:
+In order to have the joined machine registered in the AD {term}`DNS`, it needs to have an {term}`FQDN` set. You might have that already, if running the `hostname -f` command returns a full hostname with domain. If it doesn't, then set the hostname as follows:
 
 ```bash
 sudo hostnamectl hostname <yourfqdn>

how-to/security/firewalls.md

@@ -3,7 +3,7 @@
 
 The Linux kernel includes the **Netfilter** subsystem, which is used to manipulate or decide the fate of network traffic headed into or through your server. All modern Linux firewall solutions use this system for packet filtering.
 
-The kernel's packet filtering system would be of little use to administrators without a userspace interface to manage it. This is the purpose of the **`iptables`** utility: when a packet reaches your server, it will be handed off to the Netfilter subsystem for acceptance, manipulation, or rejection based on the rules supplied to it from the userspace (via `iptables`). Thus, `iptables` is all you need to manage your firewall, if you're familiar with it, but many frontends are available to simplify the task. We'll take a look at the default frontend used in Ubuntu here.
+The kernel's packet filtering system would be of little use to administrators without a userspace interface to manage it. This is the purpose of the **`iptables`** utility: when a packet reaches your server, it will be handed off to the Netfilter subsystem for acceptance, manipulation, or rejection based on the rules supplied to it from the userspace (via `iptables`). Thus, `iptables` is all you need to manage your firewall, if you're familiar with it, but many {term}`frontends <frontend>` are available to simplify the task. We'll take a look at the default frontend used in Ubuntu here.
 
 ## ufw - Uncomplicated Firewall
 

how-to/security/smart-card-authentication.md

@@ -200,7 +200,7 @@ To enable that process we have to configure the PAM module, add the relevant cer
 
 ## Setup guide
 
-This configuration uses SSSD as authenticatoin mechanism, and the example shown here is showing a possible usage for local users, but more complex setups using external remote identity managers such as FreeIPA, LDAP, Kerberos or others can be used.
+This configuration uses SSSD as authentication mechanism, and the example shown here is showing a possible usage for local users, but more complex setups using external remote identity managers such as {term}`FreeIPA`, LDAP, Kerberos or others can be used.
 
 Refer to [SSSD documentation](https://sssd.io/docs/introduction.html) to learn more about this.
 

how-to/software/package-management.md

@@ -67,7 +67,7 @@ For details on how to upgrade to a new Ubuntu release, see our {ref}`guide on up
 
 ## Aptitude
 
-Launching Aptitude with no command-line options will give you a menu-driven, text-based frontend to the APT system. Many of the common package management functions, such as installation, removal, and upgrade, can be performed in Aptitude with single-key commands, which are typically lowercase letters.
+Launching Aptitude with no command-line options will give you a menu-driven, text-based {term}`frontend` to the APT system. Many of the common package management functions, such as installation, removal, and upgrade, can be performed in Aptitude with single-key commands, which are typically lowercase letters.
 
 Aptitude is best suited for use in a non-graphical terminal environment to ensure the command keys work properly. You can start the menu-driven interface of Aptitude as a regular user by typing the following command at a terminal prompt:
 

how-to/sssd/troubleshooting.md

@@ -59,7 +59,7 @@ Kerberos is quite sensitive to {term}`DNS` issues. If you suspect something rela
 
 ### FQDN hostname
 
-Make sure `hostname -f` returns a fully qualified domain name (FQDN). Set it in `/etc/hostname` if necessary, and use `sudo hostnamectl set-hostname <fqdn>` to set it at runtime.
+Make sure `hostname -f` returns a {term}`fully qualified domain name (FQDN) <FQDN>`. Set it in `/etc/hostname` if necessary, and use `sudo hostnamectl set-hostname <fqdn>` to set it at runtime.
 
 ### Reverse name lookup
 

how-to/web-services/configure-apache2-settings.md

@@ -37,7 +37,7 @@ Specifies the port, and optionally the IP address, Apache2 should listen on. If
 
 ### The **ServerName** directive (optional)
 
-Specifies what FQDN your site should answer to. The default virtual host has no **ServerName** directive specified, so it will respond to all requests that do not match a ServerName directive in another virtual host. If you have just acquired the domain name `mynewsite.com` and wish to host it on your Ubuntu server, the value of the ServerName directive in your virtual host configuration file should be `mynewsite.com`.
+Specifies what {term}`FQDN` your site should answer to. The default virtual host has no **ServerName** directive specified, so it will respond to all requests that do not match a ServerName directive in another virtual host. If you have just acquired the domain name `mynewsite.com` and wish to host it on your Ubuntu server, the value of the ServerName directive in your virtual host configuration file should be `mynewsite.com`.
 
   Add this directive to the new virtual host file you created earlier (`/etc/apache2/sites-available/mynewsite.conf`).
 

reference/glossary.rst

@@ -497,19 +497,28 @@ Glossary
         Related topic(s): Observability, and Containers.
 
     FQDN
-        *Work in Progress*
+        A Fully Qualified Domain Name (FQDN) represents a complete name that specifies the exact location of a host within the :term:`DNS` hierarchy.
 
-    Freedesktop
-        *Work in Progress*
+        Related topic(s): Networking, Web services, Security, Active directory integration, and :term:`OpenLDAP`.
 
     FreeIPA
-        *Work in Progress*
+        Free Identity, Policy, and Audit (FreeIPA) is an open-source security solution for Linux/Unix-like systems that stores 
+        user identities in an :term:`LDAP` directory, manages a :term:`CA`, and enables authentication, policy enforcement, and 
+        auditing through integrations with :term:`SSSD` and :term:`Kerberos`.
+    
+        Related topic(s): Security, and :term:`OpenLDAP`.
 
     freenode
-        *Work in Progress*
+        Freenode is an open-source Internet Relay Chat (IRC) platform used by open-source communities for real-time discussions. 
 
     frontend
-        *Work in Progress*
+        A frontend is a user-friendly interface for managing a complex system.
+
+        - In firewall management, a frontend like `ufw` simplifies configuring `iptables`.
+        - In QEMU/KVM graphics, a frontend is the virtual graphic adapter presented to the guest OS, allowing it to process and store graphical output in memory. The guest OS treats it like a GPU, while the host determines how to display the output using the :term:`backend`.
+        - In :term:`LDAP`, the frontend is a unique database that defines global default settings, such as who the admin user is, who can access database entries, or the limit on the number of search results. These settings apply to all LDAP databases inside :term:`slapd`, unless overridden.
+
+        Related topic(s): Virtualization and containers, Security, and :term:`OpenLDAP`.
 
     fsck
         *Work in Progress*