wxVector<T> is header-based, use @nolibrary

[wxWidgets.git] / docs / doxygen / overviews / filesystem.h

diff --git a/docs/doxygen/overviews/filesystem.h b/docs/doxygen/overviews/filesystem.h
index 67c389dbdad96298deeb37a888bd06ceef14d366..f48a446fce13b45ba201e119adff4458e26aa7a9 100644 (file)
--- a/docs/doxygen/overviews/filesystem.h
+++ b/docs/doxygen/overviews/filesystem.h
@@ -6,9 +6,9 @@
 // Licence:     wxWindows license
 /////////////////////////////////////////////////////////////////////////////
 
-/*!
+/**
 
- @page overview_fs wxFileSystem overview
+ @page overview_fs wxFileSystem Overview
 
  The wxHTML library uses a @b virtual file systems mechanism
  similar to the one used in Midnight Commander, Dos Navigator,
@@ -30,13 +30,13 @@
 
  Three classes are used in order to provide virtual file systems mechanism:
 
- @li The #wxFSFile class provides information
+ @li The wxFSFile class provides information
      about opened file (name, input stream, mime type and anchor).
- @li The #wxFileSystem class is the interface.
+ @li The wxFileSystem class is the interface.
      Its main methods are ChangePathTo() and OpenFile(). This class
      is most often used by the end user.
- @li The #wxFileSystemHandler is the core
-     of virtual file systems mechanism. You can derive your own handler and pass 
+ @li The wxFileSystemHandler is the core
+     of virtual file systems mechanism. You can derive your own handler and pass
      it to the VFS mechanism. You can derive your own handler and pass it to
      wxFileSystem's AddHandler() method. In the new handler you only need to
      override the OpenFile() and CanOpen() methods.
@@ -89,7 +89,7 @@
  @li @b wxMemoryFSHandler:
      This handler allows you to access
      data stored in memory (such as bitmaps) as if they were regular files.
-     See @ref memoryfshandler_overview for details.
+     See wxMemoryFSHandler for details.
      Include file is wx/fs_mem.h. URL is prefixed with memory:, e.g.
      "memory:myfile.htm"