From a56cf4389754b577b86ca14d47a5dc7bf97ff2d1 Mon Sep 17 00:00:00 2001 From: "Robin.Mueller" Date: Thu, 4 Mar 2021 18:22:32 +0100 Subject: [PATCH] another rwadme update --- doc/README-localpools.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/README-localpools.md b/doc/README-localpools.md index 4ac2a4d8b..96ae2d0af 100644 --- a/doc/README-localpools.md +++ b/doc/README-localpools.md @@ -21,8 +21,8 @@ shown above so the steps required are altered slightly. ### Storing and Accessing pool data The pool manager is responsible for thread-safe access of the pool data, but the actual -access to the pool data from the point of view of a mission software developer is in form of -proxy classes like pool variable classes. These classes store a copy +access to the pool data from the point of view of a mission software developer happens via proxy +classes like pool variable classes. These classes store a copy of the pool variable with the matching datatype and copy the actual data from the local pool on a `read` call. Changed variables can then be written to the local pool with a `commit` call. The `read` and `commit` calls are thread-safe and can be called concurrently from data creators