Skip to content

Conversation

@oreoluwa212
Copy link
Contributor

@oreoluwa212 oreoluwa212 commented Jan 29, 2025

Writer's Checklist

/claim #49
/fixes #49
Starter Repository

Writing Structure

  • Use short sentences and paragraphs, and include bucket brigades.
  • Include more than two descriptive H2 headings to organize content.
  • Capitalize headings according to the AP Stylebook
    (use this tool)
  • Include an introduction with at least two paragraphs before the first H2
    section.
  • Use appropriate formatting (bold, italic, underline), notes, quotes,
    TLDRs, and key points.
  • Incorporate code elements and Markdown format where appropriate.
  • Ensure at least one visual element per “screen” of the article
    (screenshots, diagrams, tables, graphs, lists, sidenotes, blockquotes).

Fact-Checking

  • Verify all facts and data points included in the article.

Asset Management

  • Save images in the /assets folder.
  • Follow naming conventions:
    YYYYMMDD_title_of_the_article_IMG_NAME_NO.png.
  • (Optional) Create a GitHub repo for the code referenced in the article and
    share it.
  • (Optional) Include a link to this Loom video in the PR comments.

Interlinking

Glossary/Definitions

  • Create new definition in /defitnitions folder.

Review and Edit

  • Ensure articles address the needs of the target audience and their search
    intent.
  • Read the article out loud to catch any awkward phrasing.
  • Run the draft through Grammarly or a similar
    grammar tool.
  • Double-check adherence to the style guide and repository guidelines.
  • Use the name of the article for the title of the PR.

@oreoluwa212
Copy link
Contributor Author

oreoluwa212 commented Jan 29, 2025

@mojafa here is the clean PR , kindly review

#135 can be closed

@mojafa
Copy link
Contributor

mojafa commented Jan 29, 2025

@oreoluwa212 nice. all works well. PR LGTM.

@nkkko PR LGTM.

Screenshot 2025-01-30 at 00 07 17

Signed-off-by: oreoluwa212 <oreoluwaajayyiruth@gmail.com>
Signed-off-by: oreoluwa212 <oreoluwaajayyiruth@gmail.com>
Signed-off-by: oreoluwa212 <oreoluwaajayyiruth@gmail.com>

### Introduction

With the release of Phi-3.5, Phi-3 Labs has introduced advanced features for AI and machine learning research. This guide walks you through how to configure and run Phi-3.5 Labs samples in a Daytona environment using .NET, ensuring a seamless development experience.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Phi-3 labs? Microsoft developed phi-3. This first sentence is an immediate signal of low effort, sorry.

@nibzard
Copy link
Contributor

nibzard commented Jan 30, 2025

No clear understanding from the article what Phi-3 really is. Thanks.

@nibzard nibzard closed this Jan 30, 2025
@oreoluwa212
Copy link
Contributor Author

No clear understanding from the article what Phi-3 really is. Thanks.

@nkkko I am sorry the introduction is not up to the expected standard but I actually did put an effort into this issue. If my PR can be re-opened, I am certain that the article will be better after making proper adjustments. Or do I open a new PR, kindly advise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Using Phi-3 and .NET Development in Daytona

3 participants