2) Do not add trailing punctuation to headings.

### Quotes

1) Keep quote style consistent with the existing Korean docs.
2) Never change quotes inside inline code, code blocks, URLs, or file paths.

### Ellipsis

1) Keep ellipsis style consistent with existing Korean docs (often `...`).
2) Never change `...` in code, URLs, or CLI examples.

2) In the French docs, guillemets are written without extra spaces: use «texte», not « texte ».

3) Do not convert quotes inside code blocks, inline code, paths, URLs, or anything wrapped in backticks.

Examples:

    Source (English):

        «««
        "Hello world"
        “Hello Universe”
        "He said: 'Hello'"

1 disk2/testbucket/file/xl.meta XL2 Æ X ¨Versions‘‚¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ Ÿl;âF?Gq¦Ç ºª?ò¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDist” ¨CSumAlgo ¨PartNums‘ ©PartETags‘ ©PartSizes‘Ò ªPartASizes‘Ò ¤SizeÒ ¥MTimeÓ ð ÞÍ &˜§MetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ fffb6377948ebea75ad2¬content-type¸application/octet-streamÎ7£ï; disk1/testbucket/file/xl.meta 䱘′ ÆĀ腘嚨牥楳湯酳ꒂ祔数ꔁ㉖扏 ᄀ䦢쑄 ꐀ䑄物Ⴤ沟㽆煇잦Вꪺ䖦䅣杬ů䖣䵣ꌂ捅Ɏ䖧䉣楓敺Ò ꜀捅湉敤ɸ䖦䑣獩鑴̂Ą䎨畓䅭杬ů储牡乴浵酳꤁慐瑲呅条酳ꦠ慐瑲楓敺酳ÒЂꨀ慐瑲十穩獥튑Ȁ 厤穩퉥Ȁ 䶥楔敭ᛓ翰췞☝Ꞙ敍慴祓腳碼洭湩潩椭瑮牥慮⵬湩楬敮搭瑡쑡琄...

        }

        println(buildResult.output)

        val richReportFile = inputBuildDir.resolve("binary-compatibility/build/japi/japi.html").apply {
            assertTrue("Rich report file doesn't exist", isFile)
        }

        return CheckResult(failure, scrapeRichReport(richReportFile), buildResult).apply {
            println(richReport.toText())
            block()
        }
    }

    /**

          localDelegate.execute(this);
        }
      } finally {
        // Important to null this out here - if we did *not* execute inline, we might still
        // run() on the same thread that called execute() - such as in a thread pool, and think
        // that it was happening inline. As a side benefit, avoids holding on to the Thread object
        // longer than necessary.
        submitting = null;
      }
    }

3) If you see backticks or any other quotes inside literal text – inside `«` and `»` –  or inside blocks of literal text – inside `«««` and `»»»` – then interpret them as literal characters, do NOT interpret them as meta characters.

The above rules are in effect now.


### Definitions of terms used in this prompt

You can use `async def` or normal `def`.

And you can declare dependencies with `async def` inside of normal `def` *path operation functions*, or `def` dependencies inside of `async def` *path operation functions*, etc.

It doesn't matter. **FastAPI** will know what to do.

/// note

                    } finally {
                        updateCheckManager.touch(metadata, repository, file);
                    }
                }

                // TODO should this be inside the above check?
                // touch file so that this is not checked again until interval has passed
                if (file.exists()) {
                    file.setLastModified(System.currentTimeMillis());

          localDelegate.execute(this);
        }
      } finally {
        // Important to null this out here - if we did *not* execute inline, we might still
        // run() on the same thread that called execute() - such as in a thread pool, and think
        // that it was happening inline. As a side benefit, avoids holding on to the Thread object
        // longer than necessary.
        submitting = null;
      }
    }

```

### More technical details { #more-technical-details }

You might have noticed that `await` can only be used inside of functions defined with `async def`.

But at the same time, functions defined with `async def` have to be "awaited". So, functions with `async def` can only be called inside of functions defined with `async def` too.

So, about the egg and the chicken, how do you call the first `async` function?