update final paragraph

KristijanArmeni · KristijanArmeni · commit 4aaeccef4f3b · 2025-01-30T14:56:11.000-05:00
diff --git a/_posts/newsletters/2025-01-30-update-dmv-rse.md b/_posts/newsletters/2025-01-30-update-dmv-rse.md
@@ -22,4 +22,4 @@ What's the one practice that’s the most efficient in order to start maintainin
 
 **Incentivizing via funding: evaluation needs to show some teeth.** Finally, an audience question moved us to more systemic leverage points: how do we incentivize sharing code and data in funding schemes and applications? The first step is to make artifact (e.g. code and data) management plans required. However, this measure alone can and will fail if the evaluation stage shows no teeth and does not directly penalize poorly thought through applications. Attendees experienced in evaluating funding proposals shared their stories of how such watered down evaluation can look like in practice.
 
-All in all, a half-hour presentation led to about an hour long, rich discussion and sharing of RSE experiences among RSEs coming from a diverse set of research environments (National Institutes of health, Naval Research Laboratory, National Labs, National Institutes of Standards and Technology, NASA, private sector). A few new participants joined the RSE Slack, and some of us connected afterwards.
+All in all, a half-hour presentation led to about an hour long, rich discussion and sharing of RSE experiences among RSEs coming from a diverse set of research environments (National Institutes of health, Naval Research Laboratory, National Labs, National Institutes of Standards and Technology, NASA, private sector...). A few new participants joined the US-RSE Slack, and some of us connected afterwards. Just what this meetup is supposed to do. Next up is a meetup in Spring, stay tuned for details!

Original file line number	Diff line number	Diff line change
`@@ -22,4 +22,4 @@ What's the one practice that’s the most efficient in order to start maintainin`
`22`	`22`
`23`	`23`	Incentivizing via funding: evaluation needs to show some teeth. Finally, an audience question moved us to more systemic leverage points: how do we incentivize sharing code and data in funding schemes and applications? The first step is to make artifact (e.g. code and data) management plans required. However, this measure alone can and will fail if the evaluation stage shows no teeth and does not directly penalize poorly thought through applications. Attendees experienced in evaluating funding proposals shared their stories of how such watered down evaluation can look like in practice.
`24`	`24`
`25`		`-All in all, a half-hour presentation led to about an hour long, rich discussion and sharing of RSE experiences among RSEs coming from a diverse set of research environments (National Institutes of health, Naval Research Laboratory, National Labs, National Institutes of Standards and Technology, NASA, private sector). A few new participants joined the RSE Slack, and some of us connected afterwards.`
	`25`	+All in all, a half-hour presentation led to about an hour long, rich discussion and sharing of RSE experiences among RSEs coming from a diverse set of research environments (National Institutes of health, Naval Research Laboratory, National Labs, National Institutes of Standards and Technology, NASA, private sector...). A few new participants joined the US-RSE Slack, and some of us connected afterwards. Just what this meetup is supposed to do. Next up is a meetup in Spring, stay tuned for details!