From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7FF8F28725E for ; Mon, 11 Aug 2025 11:22:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754911354; cv=none; b=eKI5a8qt5vTOiJTEG7WrITxLtFBC5R7q13xeHvYrb3IZr2TT4XZ7LYewMVpcKWTWDHl/uTTyWq7iQHssePpWBOL+/PCtAq7rtHT+RXcO5GC8HYSadZLRybCZPOMVrdyvcupV/Lk9KFi3d4Com75s2fursi/rTMQetbsaemXGwKc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1754911354; c=relaxed/simple; bh=yH9o/+7iQTtEc5jc6WfYbooYmTC+iDCsKE/1zeYeYwQ=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=gZUiDcCRtVnj8e0qIgJ0i1dZdLWyairqPSZ4RfB/yBLm9Uidk+0FzGyR5d60h8R98wZ3RHAN66PBk8TWvY03wjr6q1wd03BfcZKiVNtZ594G9Z16CqvdTAx6gYFAcPHMRbKrI8uyc9hDPEJCy0sm5oa6nVrdbx/46CZus+jV8wI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=QD3mXGAq; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="QD3mXGAq" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1754911351; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=FwVUSFRZ0F7GHgPHZ+J3/Ax+Q+cwf/vSatx/cEwvjzI=; b=QD3mXGAqBBI/1KrTZe6ZMvDWKdBs9KI0/JJGKfkyfBOeV/PU0NWHYkIUOJPNyoLonFL7yC iT7HPPThPWLmkaGWL4HXu24l7l62esA6IyjRewRu47VhaGsBkZ352zDgPRozKbk0FvnJMZ jC0QHZ7Xid3EHQxkUH4D1iGvO8ghliY= Received: from mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-685-k73NodGxOoSyNSYeShpbMA-1; Mon, 11 Aug 2025 07:22:28 -0400 X-MC-Unique: k73NodGxOoSyNSYeShpbMA-1 X-Mimecast-MFC-AGG-ID: k73NodGxOoSyNSYeShpbMA_1754911347 Received: from mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 02A9F1800370; Mon, 11 Aug 2025 11:22:27 +0000 (UTC) Received: from [10.22.80.50] (unknown [10.22.80.50]) by mx-prod-int-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 7812219560B4; Mon, 11 Aug 2025 11:22:24 +0000 (UTC) Date: Mon, 11 Aug 2025 13:22:18 +0200 (CEST) From: Mikulas Patocka To: Shubham Sharma cc: agk@redhat.com, snitzer@kernel.org, corbet@lwn.net, msakai@redhat.com, dm-devel@lists.linux.dev, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] docs: device-mapper :Fix typos in delay.rst and vdo-design.rst In-Reply-To: <20250810113008.27381-1-slopixelz@gmail.com> Message-ID: References: <20250810113008.27381-1-slopixelz@gmail.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Scanned-By: MIMEDefang 3.0 on 10.30.177.12 Applied, thanks. Mikulas On Sun, 10 Aug 2025, Shubham Sharma wrote: > Fixed the following typos in device-mapper documentation: > - explicitely -> explicitly > - approriate -> appropriate > > Signed-off-by: Shubham Sharma > --- > Documentation/admin-guide/device-mapper/delay.rst | 2 +- > Documentation/admin-guide/device-mapper/vdo-design.rst | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/admin-guide/device-mapper/delay.rst b/Documentation/admin-guide/device-mapper/delay.rst > index 4d667228e744..982136160d6f 100644 > --- a/Documentation/admin-guide/device-mapper/delay.rst > +++ b/Documentation/admin-guide/device-mapper/delay.rst > @@ -18,7 +18,7 @@ Table line has to either have 3, 6 or 9 arguments: > to write and flush operations on optionally different write_device with > optionally different sector offset > > -9: same as 6 arguments plus define flush_offset and flush_delay explicitely > +9: same as 6 arguments plus define flush_offset and flush_delay explicitly > on/with optionally different flush_device/flush_offset. > > Offsets are specified in sectors. > diff --git a/Documentation/admin-guide/device-mapper/vdo-design.rst b/Documentation/admin-guide/device-mapper/vdo-design.rst > index 3cd59decbec0..faa0ecd4a5ae 100644 > --- a/Documentation/admin-guide/device-mapper/vdo-design.rst > +++ b/Documentation/admin-guide/device-mapper/vdo-design.rst > @@ -600,7 +600,7 @@ lock and return itself to the pool. > All storage within vdo is managed as 4KB blocks, but it can accept writes > as small as 512 bytes. Processing a write that is smaller than 4K requires > a read-modify-write operation that reads the relevant 4K block, copies the > -new data over the approriate sectors of the block, and then launches a > +new data over the appropriate sectors of the block, and then launches a > write operation for the modified data block. The read and write stages of > this operation are nearly identical to the normal read and write > operations, and a single data_vio is used throughout this operation. > -- > 2.43.0 >