Update README.md

Author: Desperationis

README.md

@@ -13,7 +13,7 @@ RobotCDocs is a tool developed for the purpose of attaching descriptions to user
 
 ## What it can do
 ### Scan / Parse Files
-RobotCDocs recursively searches for any header files in a directory. Each individual header file will be scanned for comments detailing a declaration of a function or variable, like so:
+RobotCDocs recursively searches for any header (.h) or source (.c) files in a directory. Each individual header file will be scanned for comments detailing a declaration of a function or variable, like so:
 
     FooLibrary / Foo.h - 
 
@@ -36,13 +36,13 @@ RobotCDocs recursively searches for any header files in a directory. Each indivi
 
 ![Preview Image](/Images/Foo_Image.png)
 
-### Flag Setup Functions / Variables
-Have setup functions or variables? By simply typing `[SETUP]` in any comment, the function or variable will be listed under `Setup`. 
+### Custom Naming Schemes
+By default, the documentation of a declaration will be listed under its file's name. This is seen in the above example, where Foo(parameter) is listed under the _Foo_ category. You can change the category of a declaration with the addition of `@`. In the code below, the addition of `@setup` means that the declaration will be listed under _Setup_, no matter what file it's in. As you can see, `setup` is automatically capitalized to `Setup`.
 
     FooLibrary / Foo.h - 
 
     /*
-     * [SETUP]
+     * @setup
      *
      * Very important setup function.
     */
@@ -54,24 +54,22 @@ Have setup functions or variables? By simply typing `[SETUP]` in any comment, th
 ## How it works
 RobotC's function library descriptions are located in a file called `BuiltInVariables.txt` that get parsed at runtime. The contents of this file are the functions and variables you see in the function library of RobotC.
 
-RobotCDocs allows you to add descriptions to any function or variable by writing the definition of it directly into `BuiltInVariables.txt`. The format of this function definition is similar to CSV. An example is included below. (You won't have to write at all in this dirty format, RobotCDocs does it for you)
+RobotCDocs allows you to add descriptions to any function or variable by writing the definition of it directly into `BuiltInVariables.txt`. The format of this function definition is similar to CSV. Here's a sample output of what RobotCDocs adds to `BuiltInVariables.txt`:
 
     Battery & Power Control,      Variables,          V2,            feat_NaturalLanguageInActive,           noFeatRest,                   F, A,   BackupBatteryLevel            //Returns the current voltage level of the VEX 
 
 
 ## How to use
-Using RobotCDocs is as easy as editing `setup.txt` and running `main.py`.
-
-### Editing setup.txt
+### Configuring setup.txt
 In `setup.txt`, you have to write your desired library name and a directory to be scanned:
 
     > Library Name
     [Desired Library Name]
 
-    > Where to look for files
+    > Where to look for documentation files
     [Path to folder containing header files]
 
-    > Where to find BuiltInVariables.txt
+    > Where to output BuiltInVariables.txt
     [Path to RobotC folder containing BuiltInVariables.txt]
 
 
@@ -80,10 +78,10 @@ __Example__:
     > Library Name
     Diego's Custom Library
 
-    > Where to look for files
+    > Where to look for documentation files
     C:\Users\user\Desktop\FooDocs
 
-    > Where to find BuiltInVariables.txt
+    > Where to output BuiltInVariables.txt
     C:\Program Files (x86)\Robomatter Inc\ROBOTC Development Environment 4.X\Includes
 
 
@@ -93,30 +91,39 @@ __Example__:
 
 
 ### Running main.py
-RobotCDocs has only been tested on Windows 10, and was written with python 3.7. To run in the console, simply type `python main.py` inside the root directory (assuming you installed python on your PATH). If unclear errors appear, be sure to report it in the issue tracker.
+RobotCDocs has only been tested on Windows 10, and was written with python 3.7. To run in the console, simply type `python main.py` inside the root directory (assuming you installed python on your PATH).
 
 
 ### Format of Comments
-
-Each header file should have a multi-line comment detailing the contents of the file. This is __required__. The name of the file listed inside it will hold all the functions and declarations
+RobotCDocs only parses multiline comments that precede a declaration of a function, and have an asterisk detailing the contents, such as below:
 
     /*
-     * Foo.h
+     * @Foo
      *
      * Here goes my description!
+     * Here goes another sentence!
     */
+    void NameOfFunction(); // Should be close to comment
 
-As seen above, RobotCDocs only accepts multi-line comments that start each line with an asterisk with a space on each side. These comments should appear right above function or variable declarations.
+Multiline comments that aren't preceding a declaration of a function or variable will be ignored, and a warning will be printed to the console. Same holds true for lines that don't have an asterisk, or don't have the correct number of spaces in them.
 
     /*
-     * Here goes my description!
+     * Foo.h
+     *
+     * This won't be parsed by RobotCDocs!
     */
-    void NameOfFunction(); // Should be close to comment
+    
+    /*
+     * This line will be parsed.
+     This line won't be parsed.
+       * This line won't be parsed.
+    */
+    task main();
 
-If the function should be listed under `Setup`, it should be formatted like so:
+Like previously mentioned, declarations with a custom category should have the name of the category right beside a `@`.
 
     /*
-     * [SETUP]
+     * @setup
      *
      * Here goes my description!
     */