changes after code review

also maybe make links work?

Author: folkertdev

src/attributes/codegen.md

@@ -68,18 +68,11 @@ No function prologue or epilogue are generated for the attributed function: the
 of the `naked_asm!` invocation make up the full body of a naked function.
 
 r[attributes.codegen.naked.call-stack]
-The caller must set up the call stack according to the specified calling convention before
-executing a naked function, even in contexts where setting up the call stack would ordinarily
-be unnecessary, such as when the function is inlined.
+The asm code will have a valid call stack and register state on entry as per the signature and calling convention of the function.
 
-An implementation can fulfill this requirement by guaranteeing that naked functions
-are never inlined. However, implementations are not currently required to guarantee that
-naked functions are never inlined.
-
-In the future it may become a requirement for implementations to guarantee that
-naked functions are never inlined; users must not rely on any observable behavior
-that may result from inlining. according to the specified calling convention before
-executing a naked function,
+r[attributes.codegen.naked.no-duplication]
+The asm code may not be duplicated by the compiler.
+This property is important for naked functions that define symbols in the assembly code.
 
 r[attributes.codegen.naked.unsafe-function]
 A naked function that makes use of registers in a way that does not conform
@@ -96,7 +89,7 @@ r[attributes.codegen.naked.track_caller]
 A naked function cannot be attributed by the [`track_caller`](#the-track_caller-attribute) attribute.
 
 r[attributes.codegen.naked.testing]
-A naked function cannot be attributed by [the testing attributes](../testing.md).
+A naked function cannot be attributed by [the testing attributes](attributes/testing.md).
 
 ## The `no_builtins` attribute
 

src/inline-assembly.md

@@ -80,7 +80,7 @@ Note that in some cases the compiler may choose to emit the assembly code as a s
 
 r[asm.scope.naked_asm]
 With the `naked_asm!` macro, the assembly code is emitted in a function scope and constitutes the full assembly code of a function.
-The `naked_asm!` macro is only allowed in [naked functions](../attributes/codegen.md#the-naked-attribute).
+The `naked_asm!` macro is only allowed in [naked functions](attributes/codegen.md#the-naked-attribute).
 
 r[asm.scope.global_asm]
 With the `global_asm!` macro, the assembly code is emitted in a global scope, outside a function.
@@ -588,7 +588,7 @@ r[asm.options.checks.noreturn]
 - It is a compile-time error to specify `noreturn` on an asm block with outputs.
 
 r[asm.options.naked_asm-restriction]
-`global_asm!` only supports the `att_syntax` and `raw` options.
+`naked_asm!` only supports the `att_syntax` and `raw` options.
 The remaining options are not meaningful because the inline assembly defines the whole function body.
 
 r[asm.options.global_asm-restriction]
@@ -719,7 +719,7 @@ r[asm.naked-rules.reg-not-input]
     Notably it is not the same as an LLVM `undef` which can have a different value every time you read it (since such a concept does not exist in assembly code).
 
 r[asm.naked-rules.reg-not-output]
-- Any callee-saved registers must have the same value upon exiting the asm block as they had on entry, otherwise behavior is undefined.
+- Any callee-saved registers must have the same value upon return as they had on entry, otherwise behavior is undefined.
   - Caller-saved registes may be used freely, even if they are not used for the return value.
 
 r[asm.naked-rules.unwind]
@@ -728,22 +728,13 @@ r[asm.naked-rules.unwind]
 
 r[asm.naked-rules.noreturn]
 - Behavior is undefined if execution falls through to the end of the asm block.
+    - the assembly code is expected to contain a return instruction or to diverge
 
 r[asm.naked-rules.mem-same-as-ffi]
 - The set of memory locations that assembly code is allowed to read and write are the same as those allowed for an FFI function.
   - Refer to the unsafe code guidelines for the exact rules.
   - These rules do not apply to memory which is private to the asm code, such as stack space allocated within the asm block.
 
-r[asm.naked-rules.black-box]
-- The compiler cannot assume that the instructions in the asm are the ones that will actually end up executed.
-  - This effectively means that the compiler must treat the `naked_asm!` as a black box and only take the interface specification into account, not the instructions themselves.
-  - Runtime code patching is allowed, via target-specific mechanisms.
-  - However there is no guarantee that each `naked_asm!` directly corresponds to a single instance of instructions in the object file: the compiler is free to duplicate or deduplicate `naked_asm!` blocks.
-
-r[asm.naked-rules.not-exactly-once]
-- You cannot assume that an `naked_asm!` block will appear exactly once in the output binary.
-  The compiler is allowed to instantiate multiple copies of the `naked_asm!` block, for example when the function containing it is inlined in multiple places.
-
 ### Correctness and Validity
 
 r[asm.validity]