aboutsummaryrefslogtreecommitdiff
path: root/documentation/content/en/articles/rc-scripting/_index.po
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/content/en/articles/rc-scripting/_index.po')
-rw-r--r--documentation/content/en/articles/rc-scripting/_index.po59
1 files changed, 29 insertions, 30 deletions
diff --git a/documentation/content/en/articles/rc-scripting/_index.po b/documentation/content/en/articles/rc-scripting/_index.po
index 5ffc6b104b..f90baeddb2 100644
--- a/documentation/content/en/articles/rc-scripting/_index.po
+++ b/documentation/content/en/articles/rc-scripting/_index.po
@@ -7,7 +7,7 @@
msgid ""
msgstr ""
"Project-Id-Version: FreeBSD Documentation VERSION\n"
-"POT-Creation-Date: 2022-07-07 23:23-0300\n"
+"POT-Creation-Date: 2023-05-21 14:43-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -145,23 +145,22 @@ msgid ""
"article by Luke Mewburn>>, and the [.filename]#rc.d# components are "
"documented in great detail in <<manpages, the respective manual pages>>. "
"However, it might not appear obvious to an [.filename]#rc.d# newbie how to "
-"tie the numerous bits and pieces together in order to create a well-styled "
-"script for a particular task. Therefore this article will try a different "
-"approach to describe [.filename]#rc.d#. It will show which features should "
-"be used in a number of typical cases, and why. Note that this is not a how-"
-"to document because our aim is not at giving ready-made recipes, but at "
-"showing a few easy entrances into the [.filename]#rc.d# realm. Neither is "
-"this article a replacement for the relevant manual pages. Do not hesitate "
-"to refer to them for more formal and complete documentation while reading "
-"this article."
+"tie the numerous bits and pieces together to create a well-styled script for "
+"a particular task. Therefore this article will try a different approach to "
+"describe [.filename]#rc.d#. It will show which features should be used in a "
+"number of typical cases, and why. Note that this is not a how-to document "
+"because our aim is not at giving ready-made recipes, but at showing a few "
+"easy entrances into the [.filename]#rc.d# realm. Neither is this article a "
+"replacement for the relevant manual pages. Do not hesitate to refer to them "
+"for more formal and complete documentation while reading this article."
msgstr ""
#. type: Plain text
#: documentation/content/en/articles/rc-scripting/_index.adoc:105
msgid ""
"There are prerequisites to understanding this article. First of all, you "
-"should be familiar with the man:sh[1] scripting language in order to master "
-"[.filename]#rc.d#. In addition, you should know how the system performs "
+"should be familiar with the man:sh[1] scripting language to master [."
+"filename]#rc.d#. In addition, you should know how the system performs "
"userland startup and shutdown tasks, which is described in man:rc[8]."
msgstr ""
@@ -183,9 +182,9 @@ msgstr ""
#. type: Plain text
#: documentation/content/en/articles/rc-scripting/_index.adoc:114
msgid ""
-"A little consideration before starting `$EDITOR` will not hurt. In order to "
-"write a well-tempered [.filename]#rc.d# script for a system service, we "
-"should be able to answer the following questions first:"
+"A little consideration before starting `$EDITOR` will not hurt. To write a "
+"well-tempered [.filename]#rc.d# script for a system service, we should be "
+"able to answer the following questions first:"
msgstr ""
#. type: Plain text
@@ -287,12 +286,12 @@ msgstr ""
#. type: delimited block = 4
#: documentation/content/en/articles/rc-scripting/_index.adoc:162
msgid ""
-"In order to be properly managed by the [.filename]#rc.d# framework, its "
-"scripts need to be written in the man:sh[1] language. If you have a service "
-"or port that uses a binary control utility or a startup routine written in "
-"another language, install that element in [.filename]#/usr/sbin# (for the "
-"system) or [.filename]#/usr/local/sbin# (for ports) and call it from a man:"
-"sh[1] script in the appropriate [.filename]#rc.d# directory."
+"To be properly managed by the [.filename]#rc.d# framework, its scripts need "
+"to be written in the man:sh[1] language. If you have a service or port that "
+"uses a binary control utility or a startup routine written in another "
+"language, install that element in [.filename]#/usr/sbin# (for the system) or "
+"[.filename]#/usr/local/sbin# (for ports) and call it from a man:sh[1] script "
+"in the appropriate [.filename]#rc.d# directory."
msgstr ""
#. type: delimited block = 4
@@ -375,8 +374,8 @@ msgstr ""
#. type: delimited block = 4
#: documentation/content/en/articles/rc-scripting/_index.adoc:207
msgid ""
-"To make the code in [.filename]#rc.d# more uniform, it is common to use `"
-"${name}` wherever appropriate. Thus a number of lines can be just copied "
+"To make the code in [.filename]#rc.d# more uniform, it is common to use "
+"`${name}` wherever appropriate. Thus a number of lines can be just copied "
"from one script to another."
msgstr ""
@@ -826,8 +825,8 @@ msgstr ""
#: documentation/content/en/articles/rc-scripting/_index.adoc:445
msgid ""
"&#10122; Additional arguments to `$command` can be passed in "
-"`command_args`. They will be added to the command line after `"
-"$mumbled_flags`. Since the final command line is passed to `eval` for its "
+"`command_args`. They will be added to the command line after "
+"`$mumbled_flags`. Since the final command line is passed to `eval` for its "
"actual execution, input and output redirections can be specified in "
"`command_args`."
msgstr ""
@@ -1571,11 +1570,11 @@ msgstr ""
#. type: delimited block = 4
#: documentation/content/en/articles/rc-scripting/_index.adoc:825
msgid ""
-"An man:sh[1] programmer ought to understand the subtle difference between `"
-"$*` and `$@` as the ways to designate all positional parameters. For its in-"
-"depth discussion, refer to a good handbook on man:sh[1] scripting. _Do not_ "
-"use the expressions until you fully understand them because their misuse "
-"will result in buggy and insecure scripts."
+"An man:sh[1] programmer ought to understand the subtle difference between "
+"`$*` and `$@` as the ways to designate all positional parameters. For its "
+"in-depth discussion, refer to a good handbook on man:sh[1] scripting. _Do "
+"not_ use the expressions until you fully understand them because their "
+"misuse will result in buggy and insecure scripts."
msgstr ""
#. type: delimited block = 4