Fix typos and update metadata in documentation

Corrected several typos in the Linux guest and distributed usage documentation, and updated the SKILLS.md file with front matter metadata for improved clarity and structure.

Author: doomedraven

SKILLS.md

@@ -1,3 +1,8 @@
+---
+name: cape-sandbox-developer
+description: Comprehensive guide for architecture, development patterns, and advanced troubleshooting in CAPE Sandbox (v2).
+---
+
 # CAPE Sandbox Developer Skills & Architecture Guide
 
 This document outlines the architectural structure, core concepts, and development patterns for the CAPE Sandbox (v2). It serves as a guide for extending functionality, debugging, and maintaining the codebase.
@@ -205,4 +210,4 @@ CAPE stores unstructured analysis results in the `analysis` collection.
 ```bash
 mongo cuckoo
 db.analysis.find({"info.id": 123}, {"behavior.summary": 1}).pretty()
-```
+```

docs/book/src/installation/guest/linux.rst

@@ -2,7 +2,7 @@
 Installing the Linux guest
 ==========================
 
-Linux guests doesn't have official CAPAE support!
+Linux guests don't have official CAPE support!
 First, prepare the networking for your machinery platform on the host side.
 
 .. This has not been tested recently:

docs/book/src/usage/dist.rst

@@ -164,7 +164,7 @@ or::
 Submit a new analysis task
     The method of submission is always the same: by REST API or via web GUI, both only pointing to the "master node".
 
-Get the report of a task should be requested throw master node integrated /api/
+Get the report of a task should be requested through the master node integrated /api/
 
 Proposed setup
 ==============

docs/book/src/usage/monitor.rst

@@ -8,7 +8,7 @@ What make CAPE's debugger unique among Windows debuggers is the fact that it has
 
 The debugger is not interactive, its actions are pre-determined upon submission and the results can be found in the debugger log which is presented in a dedicated tab in the UI.
 
-Th following is a quick guide on getting started with the debugger.
+The following is a quick guide on getting started with the debugger.
 
 Breakpoints: bp0, bp1, bp2, bp3
 ===============================