knownbugs in rails_breadcrumbs-0.5.4 vs knownbugs in rails_breadcrumbs-0.5.5

@@ -1,17 +1,17 @@
-Introduction:
-To see the latest list of the known bugs please visit the Known bugs page at www.majoron.com.
-
-Legend:
-Follow notation is used at change log, roadmap and known bugs. Each bug begins with a version,
-then follow category of the bug inside {}. It can be bug report, feature request and etc.
-Then follow component inside []. After follow bug number at bug tracking system between // signs.
-And then follow a short description of the bug.
-
-Example:
-For example bug: "1.0 { Feature Request } [ AntHill ] / 380 / STLport support required" means
-that bug was created for 1.0 version of the AntHill component, bug is feature request with
-380 number at bug tracking system. And bug requires STLPort support implementation.
-
- Version 0.5
- -----------
-0.5 { Bug Report } [ AuxiliaryAddons ] / X / There isn't known bugs
+Introduction:
+To see the latest list of the known bugs please visit the Known bugs page at www.majoron.com.
+
+Legend:
+Follow notation is used at change log, roadmap and known bugs. Each bug begins with a version,
+then follow category of the bug inside {}. It can be bug report, feature request and etc.
+Then follow component inside []. After follow bug number at bug tracking system between // signs.
+And then follow a short description of the bug.
+
+Example:
+For example bug: "1.0 { Feature Request } [ AntHill ] / 380 / STLport support required" means
+that bug was created for 1.0 version of the AntHill component, bug is feature request with
+380 number at bug tracking system. And bug requires STLPort support implementation.
+
+ Version 0.5
+ -----------
+0.5 { Bug Report } [ AuxiliaryAddons ] / X / There isn't known bugs