From a20ae51422f5218977d189e951610c0d4a47a06b Mon Sep 17 00:00:00 2001 From: Rosalyn Metz Date: Thu, 29 Jan 2026 12:14:52 -0500 Subject: [PATCH] fix line length issue --- draft/implementation-notes/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/draft/implementation-notes/index.md b/draft/implementation-notes/index.md index 262e804..1a65f76 100644 --- a/draft/implementation-notes/index.md +++ b/draft/implementation-notes/index.md @@ -586,8 +586,8 @@ layout to an OCFL Storage Root. the Workspace that is the same as its eventual storage path in the OCFL Storage Root. This means that it is easy for clients to determine if an object is being updated and also provides a mechanism to implement objects with mutable current versions without violating OCFL assumptions. When updating an OCFL Object, it is useful to make a copy of the -inventory of the most recent stable version of the object in this directory when it is created at the start of the update -operation. +inventory of the most recent stable version of the object in this directory when it is created at the start of the +update operation. * Version Assembly Directory: In this case, one version assembly directory should exist per OCFL Object at any time and updates to it should be managed by a single controlling process to avoid conflicts. If updates to multiple objects, or