From 7aa5fda40fb9e8fe80e6d2153ca2e87e9cc9083f Mon Sep 17 00:00:00 2001
From: Austin Sullivan <asully@chromium.org>
Date: Thu, 12 Jan 2023 17:54:04 +0000
Subject: [PATCH] Editorial: Don't use dot access on lock release

See https://github.com/whatwg/fs/pull/87#discussion_r1068229665
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index a9686f6..1dd1c52 100644
--- a/index.bs
+++ b/index.bs
@@ -808,11 +808,12 @@ in a [=/Realm=] |realm|, run these steps:
          Note: It is expected that this atomically updates the contents of the file on disk
          being written to.
 
-      1. [=file entry/lock/release|Release the lock=] on |stream|.[=FileSystemWritableFileStream/[[file]]=].
+      1. [=file entry/lock/release|Release the lock=] on |stream|'s
+         [=FileSystemWritableFileStream/[[file]]=].
       1. [=/Resolve=] |closeResult| with `undefined`.
    1. Return |closeResult|.
 1. Let |abortAlgorithm| be this step: [=file entry/lock/release|release the lock=] on
-   |stream|.[=FileSystemWritableFileStream/[[file]]=].
+   |stream|'s [=FileSystemWritableFileStream/[[file]]=].
 1. Let |highWaterMark| be 1.
 1. Let |sizeAlgorithm| be an algorithm that returns `1`.
 1. [=WritableStream/Set up=] |stream| with <a for="WritableStream/set up"><var