Right, you are correct.
Actually, I found the sys/dev/nvme/nvme_qpair.c has already have these defines, and the function a not accessable outside.

static const char *
get_status_string(uint16_t sct, uint16_t sc)
{
        struct nvme_status_string *entry;

        switch (sct) {
        case NVME_SCT_GENERIC:
                entry = generic_status;
                break;
        case NVME_SCT_COMMAND_SPECIFIC:
                entry = command_specific_status;
                break;
        case NVME_SCT_MEDIA_ERROR:
                entry = media_error_status;
                break;
        case NVME_SCT_PATH_RELATED:
                entry = path_related_status;
                break;
        case NVME_SCT_VENDOR_SPECIFIC:
                return ("VENDOR SPECIFIC");
        default:
                return ("RESERVED");
        }

        while (entry->sc != 0xFFFF) {
                if (entry->sc == sc)
                        return (entry->str);
                entry++;
        }
        return (entry->str);
}

Can I make it non-static?

"includes"

"summary"

"sub-commands"

"summary"

I suggest running the manpage through igor; it will identify common misspellings, and also find incorrect tags.

Thank you very much. I am happy with this tool.

"milliseconds"

Handle features just like logpage. and implement intel p3700's vendor features. It seems to be working.

Thanks. I always spell millisecond to milisecond. It's my fault.

Same typo as elsewhere.

Not clear to me whether it should be "... command includes" or "... commands include", but yes, number agreement.

"a feature" or "features", I think.

I don't think "shall" as a future imperative is common anymore, and it will likely confuse EFL users.

You need a line break after the sentence stop here.