Replace hyphen with asterisk in metrics.md

_articles/bn/metrics.md

@@ -16,12 +16,12 @@ Data, when used wisely, can help you make better decisions as an open source mai
 
 With more information, you can:
 
-- Understand how users respond to a new feature
-- Figure out where new users come from
-- Identify, and decide whether to support, an outlier use case or functionality
-- Quantify your project's popularity
-- Understand how your project is used
-- Raise money through sponsorships and grants
+* Understand how users respond to a new feature
+* Figure out where new users come from
+* Identify, and decide whether to support, an outlier use case or functionality
+* Quantify your project's popularity
+* Understand how your project is used
+* Raise money through sponsorships and grants
 
 For example, [Homebrew](https://github.com/Homebrew/brew/blob/bbed7246bc5c5b7acb8c1d427d10b43e090dfd39/docs/Analytics.md) finds that Google Analytics helps them prioritize work:
 
@@ -39,13 +39,13 @@ Before anybody can use or contribute back to your project, they need to know it
 
 If your project is hosted on GitHub, [you can view](https://help.github.com/articles/about-repository-graphs/#traffic) how many people land on your project and where they come from. From your project's page, click "Insights", then "Traffic". On this page, you can see:
 
-- **Total page views:** Tells you how many times your project was viewed
+* **Total page views:** Tells you how many times your project was viewed
 
-- **Total unique visitors:** Tells you how many people viewed your project
+* **Total unique visitors:** Tells you how many people viewed your project
 
-- **Referring sites:** Tells you where visitors came from. This metric can help you figure out where to reach your audience and whether your promotion efforts are working.
+* **Referring sites:** Tells you where visitors came from. This metric can help you figure out where to reach your audience and whether your promotion efforts are working.
 
-- **Popular content:** Tells you where visitors go on your project, broken down by page views and unique visitors.
+* **Popular content:** Tells you where visitors go on your project, broken down by page views and unique visitors.
 
 [GitHub stars](https://help.github.com/articles/about-stars/) can also help provide a baseline measure of popularity. While GitHub stars don't necessarily correlate to downloads and usage, they can tell you how many people are taking notice of your work.
 
@@ -65,8 +65,8 @@ If your project is on GitHub, navigate again to the "Traffic" page. You can use
 
 If usage is low compared to the number of people discovering your project, there are two issues to consider. Either:
 
-- Your project isn't successfully converting your audience, or
-- You're attracting the wrong audience
+* Your project isn't successfully converting your audience, or
+* You're attracting the wrong audience
 
 For example, if your project lands on the front page of Hacker News, you'll probably see a spike in discovery (traffic), but a lower conversion rate, because you're reaching everyone on Hacker News. If your Ruby project is featured at a Ruby conference, however, you're more likely to see a high conversion rate from a targeted audience.
 
@@ -84,17 +84,17 @@ Retention also requires an [inflow of new contributors](http://blog.abigailcabun
 
 Examples of community metrics that you may want to regularly track include:
 
-- **Total contributor count and number of commits per contributor:** Tells you how many contributors you have, and who's more or less active. On GitHub, you can view this under "Insights" -> "Contributors." Right now, this graph only counts contributors who have committed to the default branch of the repository.
+* **Total contributor count and number of commits per contributor:** Tells you how many contributors you have, and who's more or less active. On GitHub, you can view this under "Insights" -> "Contributors." Right now, this graph only counts contributors who have committed to the default branch of the repository.
 
 ![Contributor graph](/assets/images/metrics/repo_contributors_specific_graph.png)
 
-- **First time, casual, and repeat contributors:** Helps you track whether you're getting new contributors, and whether they come back. (Casual contributors are contributors with a low number of commits. Whether that's one commit, less than five commits, or something else is up to you.) Without new contributors, your project's community can become stagnant.
+* **First time, casual, and repeat contributors:** Helps you track whether you're getting new contributors, and whether they come back. (Casual contributors are contributors with a low number of commits. Whether that's one commit, less than five commits, or something else is up to you.) Without new contributors, your project's community can become stagnant.
 
-- **Number of open issues and open pull requests:** If these numbers get too high, you might need help with issue triaging and code reviews.
+* **Number of open issues and open pull requests:** If these numbers get too high, you might need help with issue triaging and code reviews.
 
-- **Number of _opened_ issues and _opened_ pull requests:** Opened issues means somebody cares enough about your project to open an issue. If that number increases over time, it suggests people are interested in your project.
+* **Number of _opened_ issues and _opened_ pull requests:** Opened issues means somebody cares enough about your project to open an issue. If that number increases over time, it suggests people are interested in your project.
 
-- **Types of contributions:** For example, commits, fixing typos or bugs, or commenting on an issue.
+* **Types of contributions:** For example, commits, fixing typos or bugs, or commenting on an issue.
 
 <aside markdown="1" class="pquote">
   <img src="https://avatars.githubusercontent.com/arfon?s=180" class="pquote-avatar" alt="avatar">
@@ -116,10 +116,10 @@ Consider [tracking how long it takes for you (or another maintainer) to respond
 
 You could also measure the time it takes to move between stages in the contribution process, such as:
 
-- Average time an issue remains open
-- Whether issues get closed by PRs
-- Whether stale issues get closed
-- Average time to merge a pull request
+* Average time an issue remains open
+* Whether issues get closed by PRs
+* Whether stale issues get closed
+* Average time to merge a pull request
 
 ## Use 📊 to learn about people