FIXME downgrades for omitted API docs

website/api/duk_check_stack.txt

@@ -11,7 +11,6 @@ can still occur).  The caller MUST NOT rely on being able to push more than
 <code>extra</code> values; although this is possible, such elements are
 reserved for Duktape's internal use.</p>
 
-<!--FIXME-->
 <p>Upon entry to a Duktape/C function and when outside any call
 there is an automatic reserve (of <code>DUK_API_ENTRY_STACK</code> elements)
 allocated for the caller in addition to call arguments on the value stack.

website/api/duk_del_var.txt

@@ -5,7 +5,7 @@ duk_bool_t duk_del_var(duk_context *ctx);
 [ ... varname! ] -> [ ... ]
 
 =summary
-FIXME
+XXX
 
 <p>The identifier deletion is equivalent to the Ecmascript expression:</p>
 <pre class="ecmascript-code">
@@ -16,11 +16,10 @@ delete varname
 Attempt to delete an identifier is compile time SyntaxError in strict mode
 code.  Because Duktape/C functions run in strict mode, the semantics for this
 call are currently not very useful when called from inside a Duktape/C function.
-FIXME.
 </div>
 
 =example
-FIXME
+XXX
 
 =tags
 variable

website/api/duk_has_var.txt

@@ -5,7 +5,7 @@ duk_bool_t duk_has_var(duk_context *ctx);
 [ ... varname! ] -> [ ... ]
 
 =summary
-FIXME
+XXX
 
 <p>The identifier existence check does not have a direct Ecmascript equivalent.
 The closest equivalent is:</p>
@@ -23,4 +23,4 @@ variable
 omit
 
 =example
-FIXME
+XXX

website/api/duk_put_var.txt

@@ -6,7 +6,6 @@ void duk_put_var(duk_context *ctx);
 
 =summary
 
-<!--FIXME-->
 <p>Write <code>val</code> to the identifier <code>varname</code>.  Possible outcomes:</p>
 <ul>
 <li>If identifier is found and write succeeds: XXX.</li>
@@ -18,7 +17,7 @@ void duk_put_var(duk_context *ctx);
     error occurs), throws an error.</li>
 </ul>
 
-FIXME
+XXX
 
 <p>The identifier write is equivalent to the Ecmascript expression:</p>
 <pre class="ecmascript-code">
@@ -26,7 +25,7 @@ varname = val
 </pre>
 
 =example
-FIXME
+XXX
 
 =tags
 variable