chore: sync content to repo (#9932)

Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com>

src/data/roadmaps/linux/content/checking-service-logs@FStz-bftQBK0M6zz2Bxl4.md

@@ -1,9 +1,8 @@
 # Checking Service Logs
 
-System logs are essential for troubleshooting and monitoring Linux systems. Most logs are stored in `/var/log` directory and managed by systemd. Use `journalctl` to view system logs and `journalctl -u service_name` for specific service logs. The `dmesg` command displays kernel messages. Regular log monitoring is crucial for system administration.
+Systemd captures output from all managed services and stores it in the journal, a binary log managed by journald. You can view logs for a specific service using journalctl -u service-name. Useful flags include -f to follow logs in real time, --since and --until to filter by time range, and -n to limit the number of lines shown. Logs include both stdout/stderr from the process and systemd lifecycle events.
 
 Visit the following resources to learn more:
 
-- [@article@How to Use journalctl Command to Analyze Logs in Linux](https://linuxhandbook.com/journalctl-command/)
-- [@article@journalctl — Linux manual page](https://www.man7.org/linux/man-pages/man1/journalctl.1.html)
-- [@article@Linux Log Files Location & How To View Logs Files](https://www.cyberciti.biz/faq/linux-log-files-location-and-how-do-i-view-logs-files/)
+- [@article@Journalctl Explained: How To View And Analyze Systemd Logs.](https://uptimerobot.com/knowledge-hub/logging/journalctl-explained-how-to-view-and-analyze-systemd-logs/)
+- [@article@How To Use journalctl to View and Manipulate systemd Logs on Linux](https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs)

src/data/roadmaps/linux/content/checking-service-status@xk5Xgi797HlVjdZJRfwX1.md

@@ -1,9 +1,7 @@
-# Service Status
+# Checking Service Status
 
-Service status shows the current state of Linux services including network processes, backend servers, and background applications. Use `systemctl status service_name` to check service states through systemd manager. Example: `systemctl status apache2.service` shows Apache web server status. Essential for diagnosing problems, maintaining performance, and preventing service downtimes.
+systemctl status service-name gives a real-time snapshot of a service: whether it's active, inactive, or failed; its process ID; recent log lines; and any error messages from the last run. For a quick boolean check, systemctl is-active and systemctl is-enabled return simple values suitable for use in scripts. The enabled/disabled state indicates whether the service is configured to start automatically at boot, separate from whether it's currently running.
 
 Visit the following resources to learn more:
 
-- [@article@Service Management in Linux: A Comprehensive Guide](https://medium.com/@thesureshvadde/service-management-in-linux-a-comprehensive-guide-cb4c7e81dfa9)
-- [@article@Use Systemctl Status Command to Check Service Status](https://linuxhandbook.com/systemctl-check-service-status/)
-- [@article@How to Check All Running Services in Linux](https://www.2daygeek.com/how-to-check-all-running-services-in-linux/)
+- [@article@Checking the Status of a Service Without Having an Exact Name](https://www.baeldung.com/linux/initialization-managers-service-status)

src/data/roadmaps/linux/content/killing-processes@0FLUI9r7znMqi6YKReLzD.md

@@ -1,9 +1,8 @@
-# Killing Processes
+# Kill Processes
 
-The `kill` command terminates processes in Linux by sending signals to specific Process IDs (PIDs). Use `kill [signal] PID` to terminate processes manually. Different signals provide various termination methods - SIGTERM for graceful shutdown, SIGKILL for forced termination. Process termination is essential for managing unresponsive or unwanted processes.
+The `kill` command terminates processes manually by sending specific signals to Process IDs (PIDs). Used when processes behave unexpectedly due to system bugs or accidental initiation. Syntax: `kill [signal or option] PID(s)`. Essential for Linux process management, allowing administrators to stop, pause, or terminate problematic processes and maintain system stability.
 
 Visit the following resources to learn more:
 
-- [@article@Killing Processes](https://linuxjourney.com/lesson/killing-processes)
 - [@article@Using Kill Command in Linux](https://linuxhandbook.com/kill-command/)
 - [@article@Kill Command in Linux](https://linuxize.com/post/kill-command-in-linux/)

src/data/roadmaps/linux/content/process-priorities@5anSYRhaKIs3dCLWlvZfT.md

@@ -1,6 +1,6 @@
 # Process Priorities
 
-Linux assigns priority levels to processes, affecting execution timing and resource allocation. Process priorities use "nice" values ranging from -20 (highest priority) to +19 (lowest priority) and only root can set negative nice value. The `/proc` filesystem contains process information including priorities. You can view priorities with `ps -eo pid,pri,user,comm` and modify them using `renice` command.
+Linux assigns priority levels to processes for efficient resource utilization and execution timing. Priority values ("nice" values) range from -20 (highest) to +19 (lowest priority). View priorities with `ps -eo pid,pri,user,comm`. Change priorities using `renice -5 -p [PID]`. Essential for system performance optimization and CPU resource management.
 
 Visit the following resources to learn more:
 

src/data/roadmaps/linux/content/process-signals@VkLWTvKnRXzvLGWza2v45.md

@@ -4,6 +4,5 @@ Process signals are communication mechanisms in Linux that notify processes of s
 
 Visit the following resources to learn more:
 
-- [@article@Process signals](https://linuxjourney.com/lesson/process-signals)
 - [@article@Understanding Linux Process Signals](https://www.ceos3c.com/linux/understanding-linux-process-signals-a-complete/)
 - [@article@Linux Process Signals and their meaning](https://linux-audit.com/processes/linux-process-signals/)

src/data/roadmaps/linux/content/shell-and-other-basics@8QBMyL8D5jPovxN8jyZW9.md

@@ -4,7 +4,6 @@ The Linux shell is a command-line interface that acts as an intermediary between
 
 Visit the following resources to learn more:
 
-- [@roadmap@Visit the Dedicated Shell/Bash Roadmap](https://roadmap.sh/shell-bash)
 - [@article@Learning The Shell](https://www.linuxcommand.org/lc3_lts0010.php)
 - [@article@What is a Shell in Linux](https://linuxsimply.com/what-is-a-shell-linux/)
 - [@article@Learn Linux Easily](https://linuxjourney.com)

src/data/roadmaps/linux/content/tcpip-stack@0pciSsiQqIGJh3x8465_s.md

@@ -1,6 +1,6 @@
-# TCP/IP Stack
+# TCP/IP
 
-TCP/IP (Transmission Control Protocol/Internet Protocol) is the foundational networking protocol suite that enables computer communication over networks. It consists of four layers: Network Interface, Internet, Transport, and Application. In Linux, TCP/IP is integral to the OS functionality, allowing hosts to connect and transfer data across same or different networks.
+TCP/IP (Transmission Control Protocol/Internet Protocol) forms the backbone of internet communication, allowing computers to connect and transfer data. It comprises four layers: Network Interface, Internet, Transport, and Application. Essential for Linux networking, enabling hosts to interact across networks. Use `netstat -at` to view active TCP/IP connections. Crucial for network management and troubleshooting.
 
 Visit the following resources to learn more:
 

src/data/roadmaps/linux/content/tr@O9Vci_WpUY-79AkA4HDx3.md

@@ -5,4 +5,4 @@ The `tr` command in Linux is a command-line utility that translates or substitut
 Visit the following resources to learn more:
 
 - [@article@tr Command in Linux: 6 Useful Examples](https://linuxhandbook.com/tr-command/)
-- [@article@Linux tr Command with Practical Examples](https://labex.io/tutorials/linux-linux-tr-command-with-practical-examples-422963)
+- [@article@Linux tr Command with Practical Examples](https://labex.io/tutorials/linux-linux-tr-command-with-practical-examples-422963)

src/data/roadmaps/linux/content/users-and-groups@h8wc8XEwWYHErna68w7Mg.md

@@ -1,10 +1,10 @@
 # Users and Groups
 
-User management in Linux uses groups to organize users and manage permissions efficiently. Groups are collections of users that simplify system administration by controlling access to resources like files and directories. Users can belong to multiple groups, enabling precise privilege management. Commands like `groupadd`, `groupdel`, `groupmod`, `usermod`, and `gpasswd` manage groups effectively. Proper group management is crucial for a secure and organized system environment.
+Linux user groups simplify system administration by managing collections of users with shared access rights to files and directories. Each user belongs to one or more groups, enabling privilege management without full superuser access. Management commands: `groupadd`, `groupdel`, `groupmod`, `usermod`, `gpasswd`. Essential for secure and organized system environments.
 
 Visit the following resources to learn more:
 
 - [@article@How to create, delete, and modify groups in Linux](https://www.redhat.com/sysadmin/linux-groups)
-- [@article@How to Manage Groups on Linux](https://linuxconfig.org/how-to-manage-groups-on-linux)
+- [@article@How to manage groups on Linux](https://linuxconfig.org/how-to-manage-groups-on-linux)
 - [@article@Creating, Modifying, and Deleting User Accounts](https://serveracademy.com/courses/linux-server-administration/creating-modifying-and-deleting-user-accounts/)
 - [@article@User Management in Linux: A Beginner's Guide](https://dev.to/austinozor/user-management-in-linux-a-beginners-guide-to-creating-modifying-and-deleting-users-fhf)