body.page-id-31 .wawi-release-widget__first-rect,
body.page-id-31 .wawi-release-widget__second-rect {
    display: none !important;
}

body.page-id-31 .wawi-release-widget,
body.page-id-31 .wawi-release-widget .wawi-release-widget__content {
    background-color: transparent !important;
    background-image: none !important;
}

body.page-id-31 .wawi-release-widget h3.wawi-release-widget__content--subtitle,
body.page-id-31 .wawi-release-widget .wawi-release-widget__content--subtitle {
    background-image: none !important;
    background-color: transparent !important;
    -webkit-background-clip: initial !important;
            background-clip: initial !important;
    -webkit-text-fill-color: #2722F8 !important;
    color: #2722F8 !important;
}

/* The sand page ground.

   `#wpadminbar` is excluded because it is a direct child of <body> and is
   neither a modal nor a backdrop, so it matched this selector and was repainted
   sand with `!important` -- beating WordPress's own admin-bar stylesheet. Its
   labels stay near-white, so for every logged-in editor the toolbar on this page
   rendered white-on-sand and unreadable, while every other page kept the normal
   dark bar. Invisible to logged-out visitors, which is why it went unnoticed.

   The exclusion is the narrow fix rather than dropping the child selector: one
   of the two unclassed wrappers below <body> is painted white by the theme and
   still needs this override to show the sand ground. */
body.page-id-31,
body.page-id-31 > div:not(.modal):not(.modal-backdrop):not(#wpadminbar) {
    background-color: #eeeee7 !important;
}

body.page-id-31 section.wawi-tutorial-section {
    margin-top: 0 !important;
}
body.page-id-31 section.wawi-panels-section {
    margin-bottom: 0 !important;
}

body.page-id-31 section.wawi-panels-section .wawi-panels-widget::before {
    display: none !important;
    content: none !important;
}