1 files changed, 38 insertions, 39 deletions
diff --git a/documentation/content/en/articles/linux-emulation/_index.po b/documentation/content/en/articles/linux-emulation/_index.po
index a4e50d7ae4..ea76cc08bd 100644
--- a/documentation/content/en/articles/linux-emulation/_index.po
+++ b/documentation/content/en/articles/linux-emulation/_index.po
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: FreeBSD Documentation VERSION\n"
-"POT-Creation-Date: 2022-08-07 10:21-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"
@@ -413,8 +413,8 @@ msgstr ""
 #. type: Plain text
 #: documentation/content/en/articles/linux-emulation/_index.adoc:209
 msgid ""
-"Syscalls on FreeBSD are issued by executing interrupt `0x80` with register `"
-"%eax` set to a desired syscall number with arguments passed on the stack."
+"Syscalls on FreeBSD are issued by executing interrupt `0x80` with register "
+"`%eax` set to a desired syscall number with arguments passed on the stack."
 msgstr ""
 
 #. type: Plain text
@@ -1168,11 +1168,11 @@ msgstr ""
 #: documentation/content/en/articles/linux-emulation/_index.adoc:522
 msgid ""
 "Block locks let waiters to be descheduled and blocked until the lock owner "
-"does not drop it and wakes up one or more contenders.  In order to avoid "
-"starvation issues, blocking locks do priority propagation from the waiters "
-"to the owner.  Block locks must be implemented through the turnstile "
-"interface and are intended to be the most used kind of locks in the kernel, "
-"if no particular conditions are met."
+"does not drop it and wakes up one or more contenders.  To avoid starvation "
+"issues, blocking locks do priority propagation from the waiters to the "
+"owner.  Block locks must be implemented through the turnstile interface and "
+"are intended to be the most used kind of locks in the kernel, if no "
+"particular conditions are met."
 msgstr ""
 
 #. type: Title =====
@@ -1276,7 +1276,7 @@ msgstr ""
 #. type: Plain text
 #: documentation/content/en/articles/linux-emulation/_index.adoc:553
 msgid ""
-"Scheduling barriers are intended to be used in order to drive scheduling of "
+"Scheduling barriers are intended to be used to drive scheduling of "
 "threading.  They consist mainly of three different stubs:"
 msgstr ""
 
@@ -1314,17 +1314,16 @@ msgstr ""
 #: documentation/content/en/articles/linux-emulation/_index.adoc:569
 msgid ""
 "The FreeBSD kernel has been made preemptive basically to deal with interrupt "
-"threads.  In fact, in order to avoid high interrupt latency, time-sharing "
-"priority threads can be preempted by interrupt threads (in this way, they do "
-"not need to wait to be scheduled as the normal path previews).  Preemption, "
-"however, introduces new racing points that need to be handled, as well.  "
-"Often, in order to deal with preemption, the simplest thing to do is to "
-"completely disable it.  A critical section defines a piece of code "
-"(borderlined by the pair of functions man:critical_enter[9] and man:"
-"critical_exit[9], where preemption is guaranteed to not happen (until the "
-"protected code is fully executed).  This can often replace a lock "
-"effectively but should be used carefully in order to not lose the whole "
-"advantage that preemption brings."
+"threads.  In fact, to avoid high interrupt latency, time-sharing priority "
+"threads can be preempted by interrupt threads (in this way, they do not need "
+"to wait to be scheduled as the normal path previews).  Preemption, however, "
+"introduces new racing points that need to be handled, as well.  Often, to "
+"deal with preemption, the simplest thing to do is to completely disable it.  "
+"A critical section defines a piece of code (borderlined by the pair of "
+"functions man:critical_enter[9] and man:critical_exit[9], where preemption "
+"is guaranteed to not happen (until the protected code is fully executed).  "
+"This can often replace a lock effectively but should be used carefully to "
+"not lose the whole advantage that preemption brings."
 msgstr ""
 
 #. type: Title =====
@@ -1354,11 +1353,11 @@ msgstr ""
 #. type: Plain text
 #: documentation/content/en/articles/linux-emulation/_index.adoc:584
 msgid ""
-"`sched_bind` is an API used in order to bind a thread to a particular CPU "
-"for all the time it executes the code, until a `sched_unbind` function call "
-"does not unbind it.  This feature has a key role in situations where you "
-"cannot trust the current state of CPUs (for example, at very early stages of "
-"boot), as you want to avoid your thread to migrate on inactive CPUs.  Since "
+"`sched_bind` is an API used to bind a thread to a particular CPU for all the "
+"time it executes the code, until a `sched_unbind` function call does not "
+"unbind it.  This feature has a key role in situations where you cannot trust "
+"the current state of CPUs (for example, at very early stages of boot), as "
+"you want to avoid your thread to migrate on inactive CPUs.  Since "
 "`sched_bind` and `sched_unbind` manipulate internal scheduler structures, "
 "they need to be enclosed in `sched_lock` acquisition/releasing when used."
 msgstr ""
@@ -1720,7 +1719,7 @@ msgid ""
 "auxiliary files and the implementation consists of printing a message saying "
 "that this syscall is not implemented.  The `UNIMPL` prototype is not used "
 "because we want to be able to identify the name of the syscall that was "
-"called in order to know what syscalls are more important to implement."
+"called to know what syscalls are more important to implement."
 msgstr ""
 
 #. type: Title ===
@@ -1796,14 +1795,14 @@ msgstr ""
 #. type: Plain text
 #: documentation/content/en/articles/linux-emulation/_index.adoc:782
 msgid ""
-"Many UNIX(R) derivates implement the man:ptrace[2] syscall in order to allow "
-"various tracking and debugging features.  This facility enables the tracing "
-"process to obtain various information about the traced process, like "
-"register dumps, any memory from the process address space, etc. and also to "
-"trace the process like in stepping an instruction or between system entries "
-"(syscalls and traps).  man:ptrace[2] also lets you set various information "
-"in the traced process (registers etc.).  man:ptrace[2] is a UNIX(R)-wide "
-"standard implemented in most UNIX(R)es around the world."
+"Many UNIX(R) derivates implement the man:ptrace[2] syscall to allow various "
+"tracking and debugging features.  This facility enables the tracing process "
+"to obtain various information about the traced process, like register dumps, "
+"any memory from the process address space, etc. and also to trace the "
+"process like in stepping an instruction or between system entries (syscalls "
+"and traps).  man:ptrace[2] also lets you set various information in the "
+"traced process (registers etc.).  man:ptrace[2] is a UNIX(R)-wide standard "
+"implemented in most UNIX(R)es around the world."
 msgstr ""
 
 #. type: Plain text
@@ -2358,11 +2357,11 @@ msgstr ""
 msgid ""
 "This will load the content of the `%edx` register into memory location "
 "0x1244.  Some segment registers have a special use, for example `%cs` is "
-"used for code segment and `%ss` is used for stack segment but `%fs` and `"
-"%gs` are generally unused.  Segments are either stored in a global GDT table "
-"or in a local LDT table.  LDT is accessed via an entry in the GDT.  The LDT "
-"can store more types of segments.  LDT can be per process.  Both tables "
-"define up to 8191 entries."
+"used for code segment and `%ss` is used for stack segment but `%fs` and "
+"`%gs` are generally unused.  Segments are either stored in a global GDT "
+"table or in a local LDT table.  LDT is accessed via an entry in the GDT.  "
+"The LDT can store more types of segments.  LDT can be per process.  Both "
+"tables define up to 8191 entries."
 msgstr ""
 
 #. type: Title ====