Updated FAQs

Minor corrections are made in the FAQ answers

Author: Alagappan21

README.md

@@ -78,7 +78,7 @@ These metrics indicate that yc-360 script can safely run in production environme
 <details>
   <summary><strong>3. Is it Safe to Run yc-360 Script in Production Environments?</strong></summary>
 
-Absolutely. The yc-360 script is a non-intrusive, read-only script. It doesn’t modify any application or system configuration. It only reads and collects diagnostics and is safe to run even in high-availability production environments.
+Absolutely. The yc-360 script is a non-intrusive, script. It doesn’t modify any application or system configuration. It only reads and collects diagnostics and is safe to run even in high-availability production environments.
 </details>
 
 <details>
@@ -106,7 +106,7 @@ The yc-360 script is effective in diagnosing memory leaks, GC pauses, CPU spikes
 </details>
 
 <details>
-  <summary><strong>8. . Where can I analyze the artifacts generated by the yc-360 script?</strong></summary>
+  <summary><strong>8. Where can I analyze the artifacts generated by the yc-360 script?</strong></summary>
 
 You have two options:
 
@@ -119,7 +119,7 @@ For more details, refer to the [Bundle Upload](https://docs.ycrash.io/ycrash-fea
 <details>
   <summary><strong>9. How do I Schedule yc-360 Script to Run Periodically?</strong></summary>
 
-You can schedule the script using cron (Linux/macOS), Task Scheduler (Windows), or Kubernetes CronJobs (in container environments). Just ensure the appropriate file write permissions are set in the output directory.
+You can schedule the script using cron (Linux/macOS), Task Scheduler (Windows), or Kubernetes CronJobs (in container environments). Just ensure the appropriate execution permission is set for the yc-360 script and Read/Write permissions for the output directory.
 </details>
 
 <details>