diff --git a/content/contributing/collaborating-on-github-docs/using-the-content-linter.md b/content/contributing/collaborating-on-github-docs/using-the-content-linter.md
index 0f131a5fba..b9670051d8 100644
--- a/content/contributing/collaborating-on-github-docs/using-the-content-linter.md
+++ b/content/contributing/collaborating-on-github-docs/using-the-content-linter.md
@@ -130,6 +130,21 @@ This content expires on January 28, 2022.
 This content also does not expire.
 ```
 
+Note, if you are placing the expired tags in an HTML `table` element, make sure the tag goes around the entire row and not just the cell. For example:
+
+```html
+<!-- expires 2024-06-28 -->
+<tr>
+<td>
+macOS
+</td>
+<td>
+The <code>macos-11</code> label has been deprecated and will no longer be available after 28 June 2024.
+</td>
+</tr>
+<!-- end expires 2024-06-28 -->
+```
+
 ## Suppressing linter rules
 
 Rarely, you may need to document something that violates one or more linter rules. In these cases, you can suppress rules by adding a comment to the Markdown file. You can disable all rules or specific rules. Always try to limit as few rules as possible. You can disable a rule for an entire file, for a section of a Markdown file, a specific line, or the next line.
diff --git a/src/audit-logs/lib/config.json b/src/audit-logs/lib/config.json
index fcd22bb6d2..99b75f29f3 100644
--- a/src/audit-logs/lib/config.json
+++ b/src/audit-logs/lib/config.json
@@ -3,5 +3,5 @@
     "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
     "apiRequestEvent": "This event is only available via audit log streaming."
   },
-  "sha": "cc8115d47b58275872d3585a274a2f9a638705fb"
+  "sha": "192b7f948cc86a674bfe320d91daa9d9dde67f6e"
 }
\ No newline at end of file