Suggested improvement for api/catalog

[kgoebber]

When the docs get rendered, there is a critical error in the documentation for using the regex keyword with find_time_nearest. The page renders the example for using strptime as r'_s(?P<strptime>d{13})' where in the actual code documentation it is r'_s(?P<strptime>\d{13})'. The key missing element is the slash (\) before the d{13}. The regex will not find the proper 13 digit string without the slash.

There may be more incidents of this...might be worth a more systematic check or way on rendering to ensure this doesn't persist from having correct internal documentations to missing characters in the rendered documentation.