Merge pull request #505 from bgraef/main

update systemd tutorial post

content/posts/ol/install/post-12/index.md

@@ -2,7 +2,7 @@
 title: "Use Systemd"
 date: 2021-06-23
 draft: false
-summary: "Learn to use systemd in Oracle Linux"
+summary: "Learn to use systemd to manage system services in system and user space."
 tags: ["ol","lab","tutorial","ol-install"]
 showDate: true
 ---
@@ -11,27 +11,28 @@ showDate: true
 
 :crescent_moon: [Lab](https://luna.oracle.com/lab/8a060473-bff3-4c04-9799-eb944951007c)
 
-:spiral_notepad: [Tutorial](https://docs.oracle.com//en/learn/use_systemd)
+:spiral_notepad: [Tutorial](https://docs.oracle.com//en/learn/ol-systemd)
 
 ## Details
 
-In these guides, you learn how to use the **systemctl** command line utility to manage and view systemd units that are controlled by systemd. This tutorial is targeted at users of Oracle Linux 8 or later.
+Systemd is a collection of software components that manages Oracle Linux system services and settings. During system startup, the boot process initializes as *PID 1*, which *systemd* later manages. From there, *systemd* or one of its child processes starts all subsequent processes. Just like it is the first process to start after the system boots, it is the last to finish running when shutting down the system. Administrators and users use `systemctl` as the primary management tool to interact with *systemd* services and `journalctl` for troubleshooting. 
 
-systemd is the first process that starts at boot and is the final process to terminate at system shutdown. systemd is primarily used to manage system services or processes and system initialization at boot. However, systemd is also capable of handling many other tasks and functions as well including event logging, device management, user login, task scheduling, time synchronization and system boot. Many features in systemd are not fully utilized as users may be more comfortable with alternate software for these purposes or different Linux distributions may have preferred approaches to system configuration.
+Within *systemd*, different types of *units* manage various types of system behavior or functions. For example, daemon processes or system services are run as service units, while target units usually define system states. You also have timer units to schedule tasks, similar to how you might use the system cron service, and mount units to configure a mount point instead of configuring it in the system fstab.
 
-Different types of behaviour or functions within systemd are handled in systemd units. For example, daemon processes or system services are run as service units, while system states are usually defined as target units. Timer units can be defined to schedule tasks similarly to how you might use the system cron service and a mount unit can be used to configure a mount point similarly to how you might configure a mount point in the system fstab.
-
-systemd is used to manage system level processes and functions, but it is also capable of managing processes running in user space. Users on a system can configure and manage their own services and systemd can even be configured to allow these services to continue running after the user has terminated their session.
+While *systemd* manages all system-level processes and functions, it can also manage processes running in user space. Users can manage services and timers they create without administrator access and even configure them to continue after the user session has terminated.
 
 ### Objectives
 
-  - Discover different systemd unit types
-  - Use systemd target units
-  - Learn common **systemctl** command syntax
-  - Create your own systemd timer unit in user space
-  - Configure systemd to allow user space processes to run after logout
+In this tutorial, you'll learn to:
+
+- Discover different systemd unit types
+- Use systemd target units
+- Run various systemctl commands
+- Configure systemd to allow user space processes to run after logout
 
-### What Do You Need?
+### Prerequisites
 
-  - A system with Oracle Linux installed.
+- Minimum of a single Oracle Linux system
 
+- Each system should have Oracle Linux installed and configured with:
+  - A non-root user account