diff --git a/sources/tech/RHCSA Series/RHCSA Series--Part 04--Editing Text Files with Nano and Vim or Analyzing text with grep and regexps.md b/sources/tech/RHCSA Series/RHCSA Series--Part 04--Editing Text Files with Nano and Vim or Analyzing text with grep and regexps.md
index 1529fecf2e..f3de8528fc 100644
--- a/sources/tech/RHCSA Series/RHCSA Series--Part 04--Editing Text Files with Nano and Vim or Analyzing text with grep and regexps.md	
+++ b/sources/tech/RHCSA Series/RHCSA Series--Part 04--Editing Text Files with Nano and Vim or Analyzing text with grep and regexps.md	
@@ -1,3 +1,5 @@
+FSSlc translating
+
 RHCSA Series: Editing Text Files with Nano and Vim / Analyzing text with grep and regexps – Part 4
 ================================================================================
 Every system administrator has to deal with text files as part of his daily responsibilities. That includes editing existing files (most likely configuration files), or creating new ones. It has been said that if you want to start a holy war in the Linux world, you can ask sysadmins what their favorite text editor is and why. We are not going to do that in this article, but will present a few tips that will be helpful to use two of the most widely used text editors in RHEL 7: nano (due to its simplicity and easiness of use, specially to new users), and vi/m (due to its several features that convert it into more than a simple editor). I am sure that you can find many more reasons to use one or the other, or perhaps some other editor such as emacs or pico. It’s entirely up to you.
@@ -251,4 +253,4 @@ via: http://www.tecmint.com/rhcsa-exam-how-to-use-nano-vi-editors/
 [2]:http://www.tecmint.com/file-and-directory-management-in-linux/
 [3]:http://www.tecmint.com/rhcsa-exam-reviewing-essential-commands-system-documentation/
 [4]:http://www.nano-editor.org/
-[5]:http://www.vim.org/
\ No newline at end of file
+[5]:http://www.vim.org/