rebranding...

[librewrt/.git] / bright-ben / docs / bugs.tex

diff --git a/bright-ben/docs/bugs.tex b/bright-ben/docs/bugs.tex
index 9c46b5a7e611f293ea4fc3e4a56051521fd181bb..0649782473b5de4862eebc4540015c15e614c581 100644 (file)
--- a/bright-ben/docs/bugs.tex
+++ b/bright-ben/docs/bugs.tex
@@ -1,7 +1,6 @@
-OpenWrt as an open source software opens its development to the community by
-having a publicly browseable subversion repository. The Trac software which
-comes along with a Subversion frontend,  a Wiki and a ticket reporting system 
-is used as an interface between developers, users and contributors in order to 
+LibreWRT as a free software project opens its development to the community by
+having a publicly browseable subversion repository, a Wiki and a ticket reporting
+system is used as an interface between developers, users and contributors in order to 
 make the whole development process much easier and efficient.
 
 We make distinction between two kinds of people within the Trac system:
@@ -17,16 +16,16 @@ A reporter might want to open a ticket for the following reasons:
 
 \begin{itemize}
 \item a bug affects a specific hardware and/or software and needs to be fixed
-\item a specific software package would be seen as part of the official OpenWrt repository
-\item a feature should be added or removed from OpenWrt
+\item a specific software package would be seen as part of the official LibreWRT repository
+\item a feature should be added or removed from LibreWRT
 \end{itemize}
 
 Regarding the kind of ticket that is open, a patch is welcome in those cases:
 
 \begin{itemize}
-\item new package to be included in OpenWrt
+\item new package to be included in LibreWRT
 \item fix for a bug that works for the reporter and has no known side effect
-\item new features that can be added by modifying existing OpenWrt files
+\item new features that can be added by modifying existing LibreWRT files
 \end{itemize}
 
 Once the ticket is open, a developer will take care of it, if so, the ticket is marked