NUT comments and Ss

config/linux-server/applications.md

@@ -313,7 +313,7 @@ Since SSL/TLS is not enabled by default for client-server communication, use onl
 1. Install: `apt install nut`
     - The service will fail to start since NUT is not configured yet.
 1. Set the mode: Open `/etc/nut/nut.conf` and set `MODE=netserver` for server or `MODE=netclient` for client.
-1. (Server) Add the UPS(s): Open `/etc/nut/ups.conf` and add a declaration for all UPSs (see example below).
+1. (Server) Add the UPS(s): Open `/etc/nut/ups.conf` and add a declaration for all UPSes (see example below).
     - Try using the `usbhid-ups` driver if using USB. Otherwise, check the [hardware compatibility list](https://networkupstools.org/stable-hcl.html) to find the correct driver. If the exact model isn't there, try a similar one.
     - For `usbhid-ups`, see the example below and [usbhid-ups(8)](https://networkupstools.org/docs/man/usbhid-ups.html). Set `offdelay` and `ondelay` appropriately.
     - You *may* need to modify some udev rules, but probably not.
@@ -342,12 +342,14 @@ Example USB UPS declaration for `usbhid-ups` (`/etc/nut/ups.conf`):
 
 ```
 [alpha]
+    desc = "PowerWalker VI 3000 RLE"
+    # usbhid-ups should work for most UPSes with
     driver = usbhid-ups
+    # If you have multiple UPSes connected, see usbhid-ups(8) for more specifying which USB device it should use
     port = auto
-    desc = "PowerWalker VI 3000 RLE"
-    # Sets "ups.delay.shutdown" (default 20s)
+    # Sets "ups.delay.shutdown", the delay between the shutdown command and when the UPS powers off (default 20s)
     offdelay = 60
-    # Sets "ups.delay.start" (default 30s, must be greater than offdelay)
+    # Sets "ups.delay.start", which I'm not entirely sure what it does (default 30s, must be greater than offdelay)
     ondelay = 70
 ```
 

config/linux-server/storage.md

@@ -151,7 +151,7 @@ This is just a suggestion for how to partition your main system drive. Since LVM
     - Monitors (typically one per node) for monitoring the state of itself and other nodes.
     - Managers (at least two for HA) for serving metrics and statuses to users and external services.
     - OSDs (object storage daemon) (one per disk) for handles storing of data, replication, etc.
-    - Metadata Servers (MDSs) for storing metadata for POSIX file systems to function properly and efficiently.
+    - Metadata Servers (MDSes) for storing metadata for POSIX file systems to function properly and efficiently.
 - At least three monitors are required for HA, because of quorum.
 - Each node connects directly to OSDs when handling data.
 - Pools consist of a number of placement groups (PGs) and OSDs, where each PG uses a number of OSDs.

index.md

@@ -99,7 +99,7 @@ Random collection of config notes and miscellaneous theory. Technically not a wi
 
 ### General
 
-- [Database Management Systems (DBMSs)](se/general/dbmses/)
+- [Database Management Systems (DBMSes)](se/general/dbmses/)
 - [Licenses](se/general/licenses/)
 
 ### Languages

se/general/dbmses.md

@@ -1,20 +1,20 @@
 ---
-title: Database Management Systems (DBMSs)
+title: Database Management Systems (DBMSes)
 breadcrumbs:
 - title: Software Engineering
 - title: General
 ---
 {% include header.md %}
 
-A very brief comparison of different database management systems (DBMSs).
+A very brief comparison of different database management systems (DBMSes).
 
-## Relational DBMSs (RDBMSs)
+## Relational DBMSes (RDBMSes)
 
-- RDBMSs are based on tables consisting of rows and columns, and it thus apropriate for structured data.
-- RDBMSs require the core properties atomicity, consistency, isolation and durability (ACID).
+- RDBMSes are based on tables consisting of rows and columns, and it thus apropriate for structured data.
+- RDBMSes require the core properties atomicity, consistency, isolation and durability (ACID).
 - Normalization is heavily used (by the user) to remove data redundancy.
 - The need for consistency (and other properties) may hinder horizontal scaling.
-- Most RDBMSs use their own variation of standard SQL, with both extra and missing features.
+- Most RDBMSes use their own variation of standard SQL, with both extra and missing features.
 
 ### SQLite
 
@@ -36,14 +36,14 @@ A very brief comparison of different database management systems (DBMSs).
 - Not fully SQL compliant, lacking support for certain features.
 - Limited support for replication.
 
-## Object-Oriented DBMSs (OODBMSs)
+## Object-Oriented DBMSes (OODBMSes)
 
-- OODBMSs are based on objects from object-oriented programming and thus allows using a common representation and environment in both the application layer and database layer without the need for querying the data (unlike RDBMSs).
+- OODBMSes are based on objects from object-oriented programming and thus allows using a common representation and environment in both the application layer and database layer without the need for querying the data (unlike RDBMSes).
 
-## Object-Relational DBMSs (ORDBMSs)
+## Object-Relational DBMSes (ORDBMSes)
 
-- ORDBMSs are a hybrid of OODBMSs and RDBMSs which contains features from both.
-- Unline pure RDBMSs, they may support (e.g.) inheritance and custom data types.
+- ORDBMSes are a hybrid of OODBMSes and RDBMSes which contains features from both.
+- Unline pure RDBMSes, they may support (e.g.) inheritance and custom data types.
 
 ### PostgreSQL
 
@@ -55,10 +55,10 @@ A very brief comparison of different database management systems (DBMSs).
 
 ## NoSQL
 
-- NoSQL is an umbrella term for non-relational DBMSs and thus consists of many different categories.
+- NoSQL is an umbrella term for non-relational DBMSes and thus consists of many different categories.
 - It's aimed at non-structured data that wouldn't fit nicely in a (relational) table.
-- OODBMSs may technically be considered NoSQL, but they often contain features which make them more similar to RDBMSs.
-- While RDBMSs rely on strict consistency, NoSQL aims for eventual consistency, meaning it allows data changes to reach all database nodes in a short time rather than instantaneously. This means that the data received from the database(s) may in some cases be slightly outdated.
+- OODBMSes may technically be considered NoSQL, but they often contain features which make them more similar to RDBMSes.
+- While RDBMSes rely on strict consistency, NoSQL aims for eventual consistency, meaning it allows data changes to reach all database nodes in a short time rather than instantaneously. This means that the data received from the database(s) may in some cases be slightly outdated.
 
 ### Key-Value Stores
 
@@ -70,7 +70,7 @@ A very brief comparison of different database management systems (DBMSs).
 
 ### Columnar-Oriented Databases
 
-- Similar to RDBMSs, but splits all columns into different files. This allows for certain types of optimizations, which may improve both storage and querying for certain application types.
+- Similar to RDBMSes, but splits all columns into different files. This allows for certain types of optimizations, which may improve both storage and querying for certain application types.
 - Examples:
     - Apache Cassandra
     - Apache HBase