File 0530-persistent_term.xml-fix-grammar.patch of Package erlang

Overview Repositories Revisions Requests Users Attributes Meta

File 0530-persistent_term.xml-fix-grammar.patch of Package erlang (Revision 1fca9f2f48345e43a61098f600f2b10f)

Currently displaying revision 1fca9f2f48345e43a61098f600f2b10f , Show latest

From 05121c8e6d884ba545a354a5c00c0bf717d52e06 Mon Sep 17 00:00:00 2001
From: Mikael Pettersson <mikpelinux@gmail.com>
Date: Sat, 29 Oct 2022 13:17:36 +0200
Subject: [PATCH] persistent_term.xml: fix grammar

---
 erts/doc/src/persistent_term.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/erts/doc/src/persistent_term.xml b/erts/doc/src/persistent_term.xml
index 46cb313ff1..05449d9e22 100644
--- a/erts/doc/src/persistent_term.xml
+++ b/erts/doc/src/persistent_term.xml
@@ -50,7 +50,7 @@
 performance when updating or deleting persistent terms.</warning>
 
 Term lookup (using <seemfa
- marker="#get/1"><c>get/1</c></seemfa>), is done in constant time
+ marker="#get/1"><c>get/1</c></seemfa>) is done in constant time
 and without taking any locks, and the term is not
 copied to the heap (as is the case with terms stored in ETS
 tables).
@@ -71,7 +71,7 @@
 scan of their heaps for the term that has been deleted. While
 such scan is relatively light-weight, if there are many
 processes, the system can become less responsive until all
- process have scanned their heaps.</item>
+ processes have scanned their heaps.</item>
 
 <item>If the deleted term (or any part of it) is still used
 by a process, that process will do a major (fullsweep) garbage
@@ -146,7 +146,7 @@
 Updating or deleting a persistent term will trigger a global GC
 if the term does not fit in one machine word. Processes will be
 scheduled as usual, but all processes will be made runnable at
- once, which will make the system less responsive until all process
+ once, which will make the system less responsive until all processes
 have run and scanned their heaps for the deleted terms. One way to
 minimize the effects on responsiveness could be to minimize the
 number of processes on the node before updating or deleting a
@@ -157,7 +157,7 @@
 persistent term could be deleted or updated in the future. If a
 process holds a reference to a persistent term when the term is
 deleted, the process will be garbage collected and the term copied
- to process.
+ to the process.
 
 Avoid updating or deleting more than one persistent term at a
 time. Each deleted term will trigger its own global GC. That
-- 
2.35.3

Places

File 0530-persistent_term.xml-fix-grammar.patch of Package erlang (Revision 1fca9f2f48345e43a61098f600f2b10f)

Places