Skip to content

Commit f9de503

Browse files
committed
Fix typo in Presenter Guidelines
1 parent be99edd commit f9de503

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

_posts/2020-02-12-presenter-guidelines.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ products or services.
1212
We have some guidelines to make sure that the talk is useful and relevant for
1313
our members:
1414

15-
- You **must not** solicit investment from our audience in any way.
15+
- You **must not** solicit investment from our audience in any way.
1616
- All presentations are capped at 15 minutes, including question time.
1717
- The content of your presentation must be directly relevant to a technical
1818
audience that is interested in:
@@ -22,12 +22,12 @@ our members:
2222
interact with, tooling for developers, etc.).
2323
- Your project must be:
2424
- Technically innovative (rehashing of existing tech in a new product would
25-
not qualify, unless the implementation is demonstrably novel).
25+
not qualify, unless the implementation is demonstrably novel).
2626
- Live, or code published if it is FOSS.
2727
- You must work directly on the project and have strong understanding of its
2828
fundamentals. You should be prepared to answer technical questions about how
2929
the project is implemented.
30-
- The presentation must be centered around a live demo. Anything more then 3-5
30+
- The presentation must be centered around a live demo. Anything more than 3-5
3131
minutes of slides is not allowed without explicit approval.
3232
- Your presentation must be complete 1 week before the event. Be prepared to do
3333
a dry run of your presentation with the BitDevs organization team.

0 commit comments

Comments
 (0)