Update nep-0508.md

fix lint errors

neps/nep-0508.md

@@ -94,10 +94,12 @@ TBD
 ## Future possibilities
 
 As noted above, dynamic resharding is out of scope for this NEP and should be implemented in the future. Dynamic resharding includes the following but not limited to:
+
 * automatic determination of split boundary
 * automatic shard splitting and merging based on traffic
 
 Other useful features that can be considered as a follow up:
+
 * account colocation for low latency across account call
 * shard on demand
 
@@ -130,9 +132,9 @@ We do not expect anything to break with this change. Yet, shard splitting can in
 
 [Explain any issues that warrant further discussion. Considerations
 
-- What parts of the design do you expect to resolve through the NEP process before this gets merged?
-- What parts of the design do you expect to resolve through the implementation of this feature before stabilization?
-- What related issues do you consider out of scope for this NEP that could be addressed in the future independently of the solution that comes out of this NEP?]
+* What parts of the design do you expect to resolve through the NEP process before this gets merged?
+* What parts of the design do you expect to resolve through the implementation of this feature before stabilization?
+* What related issues do you consider out of scope for this NEP that could be addressed in the future independently of the solution that comes out of this NEP?]
 
 ## Changelog
 
@@ -146,8 +148,8 @@ We do not expect anything to break with this change. Yet, shard splitting can in
 
 > List of benefits filled by the Subject Matter Experts while reviewing this version:
 
-- Benefit 1
-- Benefit 2
+* Benefit 1
+* Benefit 2
 
 #### Concerns