Remove lots of redundant line feeds around block elements in the docs.

1 files changed, 4 insertions, 4 deletions

diff --git a/src/modules/system/Plugin.cpp b/src/modules/system/Plugin.cpp
index f63d3dfa9..33bb6c253 100644
--- a/src/modules/system/Plugin.cpp
+++ b/src/modules/system/Plugin.cpp
@@ -51,7 +51,7 @@
 		[br][br]
 		[b]Exported functions by easyplugin (C/C++-Examples):[/b][br]
 		[b]_free function[/b] [i] (needed)[/i][br][br]
-		This function is important! Since KVIrc can not free directly the memory of the dll, the plugins need the _free function so that the memory can be freed by the plugin to prevent memory-leaks.[br]
+		This function is important! Since KVIrc can not free directly the memory of the dll, the plugins need the _free function so that the memory can be freed by the plugin to prevent memory-leaks.
 		[example]
 			int _free(void * p)
 			{
@@ -70,7 +70,7 @@
 		[/example]
 		[b]_unload function[/b] [i]((optional)[/i][br][br]
 		This function will be called before the plugins is unloaded. In this function you can clean up memory or other things.
-		After this call there is no guarantee that the plugin will be kept in memory.[br]
+		After this call there is no guarantee that the plugin will be kept in memory.
 		[example]
 			int _unload()
 			{
@@ -80,7 +80,7 @@
 		[br][b]_canunload function[/b] [i](optional)[/i][br]
 		The _canunload-function will be called by KVIrc to check if it may unload the plugin.
 		If return value is true KVIrc will unload the plugin, false means he will try unloading it at the next check.[br]
-		Important: KVIrc will ignore this if unload of plugins will be forced! So you have to be sure that the _unload function of your plugins cleans up![br]
+		Important: KVIrc will ignore this if unload of plugins will be forced! So you have to be sure that the _unload function of your plugins cleans up!
 		[example]
 			int _canunload()
 			{
@@ -90,7 +90,7 @@
 		[br][b]user function[/b][br]
 		This is the general structure of a user function call.[br]
 		The important thing here is the handling of return values. To return a value to KVIrc you have to allocate memory and write the pointer to it into pBuffer.[br]
-		Have a look at the example for more details.[br]
+		Have a look at the example for more details.
 		[example]
 			int about(int argc, char * argv[], char ** pBuffer)
 			{