[Forensics-changes] [yara] 271/368: Replace "backslashes" with "forward slashes" in documentation as reported in issue #443

[Hilko Bengen]

This is an automated email from the git hooks/post-receive script.

bengen pushed a commit to annotated tag v3.5.0
in repository yara.

commit c7f00b9a2cb02e0a4e37f718d475c87f8763199e
Author: plusvic <plusvic at gmail.com>
Date:   Thu May 12 11:33:48 2016 +0200

    Replace "backslashes" with "forward slashes" in documentation as reported in issue #443
---
 docs/writingrules.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/writingrules.rst b/docs/writingrules.rst
index b43a38e..c18fd3d 100644
--- a/docs/writingrules.rst
+++ b/docs/writingrules.rst
@@ -337,7 +337,7 @@ Regular expressions
 -------------------
 
 Regular expressions are one of the most powerful features of YARA. They are
-defined in the same way as text strings, but enclosed in backslashes instead
+defined in the same way as text strings, but enclosed in forward slashes instead
 of double-quotes, like in the Perl programming language. ::
 
     rule RegExpExample1
@@ -665,7 +665,7 @@ The ``intXX`` functions read 8, 16, and 32 bits signed integers from
 Both 16 and 32 bits integer are considered to be little-endian. If you
 want to read a big-endian integer use the corresponding function ending
 in ``be``. The <offset or virtual address> parameter can be any expression returning
-an unsigned integer, including the return value of one the ``uintXX`` functions 
+an unsigned integer, including the return value of one the ``uintXX`` functions
 itself. As an example let's see a rule to distinguish PE files::
 
     rule IsPE

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/forensics/yara.git