Fixed syntax error in image tags

src/content/docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-coe.mdx

@@ -72,14 +72,13 @@ Meet to maintain an organization wide telemetry ingest target.  This can be brok
 * Team C (Monthly): 100TB
 
 This rough set of targets leaves 100TB as a buffer for uncertainty. You may also choose some specific limits based on certain highly variable telemetry. For example you may set organization or team based limits on Log or Metrics ingest.
-
 ### Monthly ingest check-ins
-<img src={<img src={monthlyingestcheckin} alt="Monthly Ingest Checkin!" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} />} alt="Observability Manger" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} />
+<img src={monthlyingestcheckin} alt="Monthly Ingest Checkin" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} />
 
 During these sessions you'll track ingest against your plan and produce action items needed to stay on target.
 
 ### Ad hoc anomaly resolution
-<img src={<img src={adhocanomalyicon} alt="Adhoc Anomaly Resolution" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} />} alt="Observability Manger" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} />
+<img src={adhocanomalyicon} alt="Ad Hoc Anomaly Resolution" style={{ height: '66px', width: '75px', verticalAlign: 'middle'}} />
 Occasionally a system refactor or organizational change could lead to an unexpected increase in data ingest.  In this scenario it may be necessary to call a meeting to address the specific topic.  Some scenarios to watch for:
 
 - A new software deployment increases log volume by 3x.