From e4451d877369d5327a81497eeb66a7b5422fb003 Mon Sep 17 00:00:00 2001
From: Dimitri Schoolwerth <dimitri.schoolwerth@gmail.com>
Date: Sun, 25 Jul 2004 17:38:46 +0000
Subject: [PATCH] fixed tex2rtf errors

git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@28500 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
---
 docs/latex/wx/socket.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/latex/wx/socket.tex b/docs/latex/wx/socket.tex
index e8741147d0..9687cbf035 100644
--- a/docs/latex/wx/socket.tex
+++ b/docs/latex/wx/socket.tex
@@ -627,7 +627,7 @@ during IO calls, so the GUI will remain blocked until the operation
 completes. If it is not used, then the application must take extra
 care to avoid unwanted reentrance.
 
-The {\bf wxSOCKET\_REUSEADDR} flag controls the use of the SO_REUSEADDR standard
+The {\bf wxSOCKET\_REUSEADDR} flag controls the use of the SO\_REUSEADDR standard
 setsockopt() flag. This flag allows the socket to bind to a port that is already in use.
 This is mostly used on UNIX-based systems to allow rapid starting and stopping of a server - 
 otherwise you may have to wait several minutes for the port to become available.
@@ -647,7 +647,7 @@ the data.
 {\bf wxSOCKET\_BLOCK} has nothing to do with the previous flags and
 it controls whether the GUI blocks.
 
-(\bf wxSOCKET\_REUSEADDR} controls special platform-specific behavior for wxServerSocket.
+{\bf wxSOCKET\_REUSEADDR} controls special platform-specific behavior for wxServerSocket.
 
 %
 % SetNotify
-- 
2.50.0

