Yet another change to table cell docs.

Author: mackron

docs/api.md

@@ -996,9 +996,7 @@ file should be opened. It can be a combination of the following flags:
 | `FS_TRUNCATE` | Only valid when used with `FS_WRITE`. If the file already exists, it will be truncated to zero length when opened. If the file does not exist, it will be created. Not compatible with `FS_APPEND`. |
 | `FS_APPEND` | Only valid when used with `FS_WRITE`. All writes will occur at the end of the file, regardless of the current cursor position. If the file does not exist, it will be created. Not compatible with `FS_TRUNCATE`. |
 | `FS_EXCLUSIVE` | Only valid when used with `FS_WRITE`. The file will be created, but if it already exists, the open will fail with FS_ALREADY_EXISTS. |
-| `FS_TRANSPARENT` | This is the default behavior. When used, files inside archives can be opened transparently. For example, "somefolder/archive.zip/file.txt" can be opened with "somefolder/file.txt" (the "archive.zip" part need not be specified). This assumes the `fs` object has been initialized with support for the relevant archive types.<br><br>Transparent mode is the slowest mode since it requires searching through the file system for archives, and then open those archives, and then searching through the archive for the file. If this is prohibitive, consider using `FS_OPAQUE` (fastest) or `FS_VERBOSE` modes instead.<br><br>Furthermore, you can consider having a rule in your application that instead of opening files inside archives from a transparent path, that you instead mount the archive, and then open all files with `FS_OPAQUE`, but with a virtual path that points to the archive. For example: <pre><code>
-fs_mount(pFS, "somefolder/archive.zip", "assets", FS_READ);
-fs_file_open(pFS, "assets/file.txt", FS_READ \| FS_OPAQUE, &pFile);</code></pre><br>Here the archive is mounted to the virtual path "assets". Because the path "assets/file.txt" is prefixed with "assets", the file system knows to look inside the mounted archive without having to search for it. |
+| `FS_TRANSPARENT` | This is the default behavior. When used, files inside archives can be opened transparently. For example, "somefolder/archive.zip/file.txt" can be opened with "somefolder/file.txt" (the "archive.zip" part need not be specified). This assumes the `fs` object has been initialized with support for the relevant archive types.<br><br>Transparent mode is the slowest mode since it requires searching through the file system for archives, and then open those archives, and then searching through the archive for the file. If this is prohibitive, consider using `FS_OPAQUE` (fastest) or `FS_VERBOSE` modes instead.<br><br>Furthermore, you can consider having a rule in your application that instead of opening files inside archives from a transparent path, that you instead mount the archive, and then open all files with `FS_OPAQUE`, but with a virtual path that points to the archive. For example: <br>    <br>    fs_mount(pFS, "somefolder/archive.zip", "assets", FS_READ);<br>    fs_file_open(pFS, "assets/file.txt", FS_READ \| FS_OPAQUE, &pFile);<br><br>Here the archive is mounted to the virtual path "assets". Because the path "assets/file.txt" is prefixed with "assets", the file system knows to look inside the mounted archive without having to search for it. |
 | `FS_OPAQUE` | When used, archives will be treated as opaque, meaning attempting to open a file from an unmounted archive will fail. For example, "somefolder/archive.zip/file.txt" will fail because it is inside an archive. This is the fastest mode, but you will not be able to open files from inside archives unless it is sourced from a mount. |
 | `FS_VERBOSE` | When used, files inside archives can be opened, but the name of the archive must be specified explicitly in the path, such as "somefolder/archive.zip/file.txt". This is faster than `FS_TRANSPARENT` mode since it does not require searching for archives. |
 | `FS_NO_CREATE_DIRS` | When opening a file in write mode, the default behavior is to create the directory structure automatically if required. When this options is used, directories will *not* be created automatically. If the necessary parent directories do not exist, the open will fail with FS_DOES_NOT_EXIST. |

tools/fsdoc.c

@@ -2004,12 +2004,12 @@ static char* fsdoc_convert_options_to_table(const char* pStr, const fs_allocatio
                                             pWrite++;
                                         }
                                     }
-                                    strcpy(pWrite, "<pre><code>");
-                                    pWrite += 11;
+                                    strcpy(pWrite, "<br>    ");
+                                    pWrite += 8;
                                     in_code_block = 1;
                                 } else if (!is_code_line && in_code_block) {
-                                    strcpy(pWrite, "</code></pre>");
-                                    pWrite += 13;
+                                    strcpy(pWrite, "<br>");
+                                    pWrite += 4;
                                     in_code_block = 0;
                                     just_closed_code_block = 1;
                                 }
@@ -2038,8 +2038,8 @@ static char* fsdoc_convert_options_to_table(const char* pStr, const fs_allocatio
                                         }
                                     }
                                 } else if (is_code_line && in_code_block && !first_desc_line) {
-                                    strcpy(pWrite, "\n");
-                                    pWrite++;
+                                    strcpy(pWrite, "<br>    ");
+                                    pWrite += 8;
                                 }
 
                                 /* Trim leading spaces from code lines */
@@ -2069,8 +2069,8 @@ static char* fsdoc_convert_options_to_table(const char* pStr, const fs_allocatio
 
                         /* Close any open code block */
                         if (in_code_block) {
-                            strcpy(pWrite, "</code></pre>");
-                            pWrite += 13;
+                            strcpy(pWrite, "<br>");
+                            pWrite += 4;
                         }
 
                         /* End the table row */