   ///
   /// Generally speaking, the application does not require cache data to operate properly, but it can use cache data to improve performance. Examples of cache data include (but are not limited to) database cache files and transient, downloadable content.
   ///
-  /// Note that the system may delete the Caches/ directory to free up disk space, so your app must be able to re-create or download these files as needed.
   /// The contents of the *Library/Caches* are **not backed up by iTunes and iCloud**.
   ///
-  /// - important: macOS apps that are sandboxed have all their *Cache* directory located at a system-defined path (typically found at *~/Library/Containers/<bundle_id>*).
+  /// Note that the system may delete the Caches/ directory to free up disk space, so your app must be able to re-create or download these files as needed.
+  ///
+  /// - important: Sandboxed *macOS* apps have all their *Caches* directory located at a system-defined path (typically found at *~/Library/Containers/<bundle_id>*).
   public class var cachesDirectory: URL {
     return try! FileManager.default.url(for: .cachesDirectory, in: .userDomainMask, appropriateFor: nil, create: true)
   }

  ///
  /// You typically put files in one of several standard subdirectories. iOS apps commonly use the *Application Support* and *Caches subdirectories*; however, you can create custom subdirectories.
  ///
  /// The contents of the *Library* directory (with the exception of the *Caches subdirectory*) are **backed up by iTunes and iCloud**.
  public class var libraryDirectory: URL {
    return try! FileManager.default.url(for: .libraryDirectory, in: .userDomainMask, appropriateFor: nil, create: true)
  }

  
  /// **Mechanica**
  ///
  /// Destroys a file or a directory at a given `path`; throws an error in cases of failure.
  ///
  /// - Parameter path: directory or file path.
  public class func destroyFileOrDirectory(atPath path: String) throws {
