README: Add Cataclysm Classic references

README.md

@@ -145,8 +145,8 @@ Supported keywords and when the code block will run:
   file.
 - `no-lib-strip`: *(not supported in Lua files)* in any build other than a
   *nolib* build.
-- `retail`,`version-retail`,`version-classic`,`version-bcc`,`version-wrath`:
-  based on game version.
+- `retail`,`version-retail`,`version-classic`,`version-bcc`,`version-wrath`,
+  `version-cata`: based on game version.
 
 `do-not-package` is a bit special. Everything between the tags, including the
 tags themselves, will always be removed from the packaged file. This will cause
@@ -218,10 +218,10 @@ on the build type:
 
 `{classic}` has some additional magic:
 
-1. It will show as the non-retail build type, so `-classic`, `-bcc`, or
-   `-wrath`.
-2. It will not be shown if "-classic" or "-bcc" or "-wrath" is in the project
-   version (tag).
+1. It will show as the non-retail build type, so `-classic`, `-bcc`, `-wrath`,
+   or `-cata`.
+2. It will not be shown if "-classic", "-bcc", "-wrath", or "-cata" is in the
+   project version (tag).
 3. If it is included in the file name (it is by default) and #2 does not apply,
    it will also be appended to the file label (i.e., the name shown in the file
    list on CurseForge).
@@ -260,10 +260,12 @@ the base interface value as it's version.
 ## Interface-Classic: 11403
 ## Interface-BCC: 20504
 ## Interface-Wrath: 30400
+## Interface-Cata: 40400
 ```
 
 Splitting the above TOC file would end up with `MyAddon_Vanilla.toc`,
-`MyAddon_TBC.toc`, `MyAddon_Wrath.toc`, and `MyAddon.toc` (retail).
+`MyAddon_TBC.toc`, `MyAddon_Wrath.toc`, `MyAddon_Cata.toc`, and `MyAddon.toc`
+(retail).
 
 If you use build version keywords (e.g., `@version-retail@` ... `@end-version-retail@`)
 for controlling what code blocks execute based on the build version, you