/**
 * Bricks' global "Custom CSS" field, moved into the child theme.
 *
 * This lived in the `customCss` key of the `bricks_global_settings` option, which means it
 * was invisible to git: it could not be reviewed, it did not travel with a deploy, and the
 * only copy was whatever each environment's database happened to hold. The rules below are
 * unchanged from that field; only the storage moved. The `bricks_global_custom_code`
 * migration step clears the option so they are never applied twice.
 *
 * The `.rich-textbox` rules use native CSS nesting, exactly as they did in the Bricks field —
 * this file is enqueued as-is and never passes through the Tailwind build, so nothing
 * flattens them.
 */
  .up-sells.upsells.products,
  .cross-sells {
    display: none;
  }

.rich-textbox {
 ol{
  li {
    list-style: auto;
    list-style-position: inside;
  }
 }
 ul {
  li {
   list-style: disc;
   list-style-position: inside;
  }
 }
 a {
              color: rgb(32 177 105 / var(--tw-text-opacity, 1));
  &:hover {
}
 }

}