From 55ddd4454665a3c66e3d5b186bc79048468d36e7 Mon Sep 17 00:00:00 2001
From: Alexey Pyltsyn <lex61rus@gmail.com>
Date: Mon, 15 Mar 2021 14:29:50 +0300
Subject: Auto fixes

---
 files/ru/web/api/storage_access_api/index.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'files/ru/web/api/storage_access_api/index.html')

diff --git a/files/ru/web/api/storage_access_api/index.html b/files/ru/web/api/storage_access_api/index.html
index f9c79c5704..b25793e407 100644
--- a/files/ru/web/api/storage_access_api/index.html
+++ b/files/ru/web/api/storage_access_api/index.html
@@ -43,7 +43,7 @@ translation_of: Web/API/Storage_Access_API
 
 <p>When <code>requestStorageAccess()</code> is called by an embedded, cross-origin document, the user agent may choose to involve the user in the decision of whether to grant storage access to the requesting origin. Prompting heuristics currently vary across the two implementers of the Storage Access API — Safari shows prompts for all embedded tracking content that has not previously received storage access, while Firefox only prompts users after a tracking origin has requested storage access on more than a threshold number of sites. See {{domxref("Document.requestStorageAccess()")}} for more details.</p>
 
-<h2 id="Отичия_реализации_в_Safari">Отичия реализации в Safari</h2>
+<h2 id="Отличия_реализации_в_Safari">Отличия реализации в Safari</h2>
 
 <p>Although the API surface is the same, websites using the Storage Access API should expect differences in the level and extent of storage access they receive between Firefox and Safari. This is caused by differences in the storage access policies implemented in the two browsers. Design properties unique to Firefox are summarized here:</p>
 
@@ -74,7 +74,7 @@ translation_of: Web/API/Storage_Access_API
 
 <h2 id="Расширение_&lt;iframe>_sandbox">Расширение &lt;iframe&gt; sandbox</h2>
 
-<p>{{htmlelement("iframe")}} <code>sandbox</code> появился новый признак, <code>allow-storage-access-by-user-activation</code>, который позволяет изолированому <code>&lt;iframe&gt;</code> использовать Storage Access API для запроса доступа к хранилищу.</p>
+<p>{{htmlelement("iframe")}} <code>sandbox</code> появился новый признак, <code>allow-storage-access-by-user-activation</code>, который позволяет изолированному <code>&lt;iframe&gt;</code> использовать Storage Access API для запроса доступа к хранилищу.</p>
 
 <h2 id="Спецификации">Спецификации</h2>
 
@@ -90,4 +90,4 @@ translation_of: Web/API/Storage_Access_API
 
 <h2 id="Смотрите_также">Смотрите также</h2>
 
-<p><a href="/en-US/docs/Web/API/Storage_Access_API/Using">Использоваие Storage Access API</a></p>
+<p><a href="/en-US/docs/Web/API/Storage_Access_API/Using">Использование Storage Access API</a></p>
-- 
cgit v1.2.3-54-g00ecf