additional links for the Romanian translation

Author: kcq

README.md

@@ -10,12 +10,13 @@ Translations:
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 ## Overview
 
-This is a basic layout for Go application projects. It's not an official standard defined by the core Go dev team; however, it is a set of common historical and emerging project layout patterns in the Go ecosystem. Some of these patterns are more popular than others. It also has a number of small enhancements along with several supporting directories common to any large enough real world application.
+This is a basic layout for Go application projects. It's `not an official standard defined by the core Go dev team`; however, it is a set of common historical and emerging project layout patterns in the Go ecosystem. Some of these patterns are more popular than others. It also has a number of small enhancements along with several supporting directories common to any large enough real world application.
 
-If you are trying to learn Go or if you are building a PoC or a toy project for yourself this project layout is an overkill. Start with something really simple (a single `main.go` file is more than enough). As your project grows keep in mind that it'll be important to make sure your code is well structured otherwise you'll end up with a messy code with lots of hidden dependencies and global state. When you have more people working on the project you'll need even more structure. That's when it's important to introduce a common way to manage packages/libraries. When you have an open source project or when you know other projects import the code from your project repository that's when it's important to have private (aka `internal`) packages and code. Clone the repository, keep what you need and delete everything else! Just because it's there it doesn't mean you have to use it all. None of these patterns are used in every single project. Even the `vendor` pattern is not universal.
+`If you are trying to learn Go or if you are building a PoC or a simple project for yourself this project layout is an overkill. Start with something really simple instead (a single `main.go` file and `go.mod` is more than enough).` As your project grows keep in mind that it'll be important to make sure your code is well structured otherwise you'll end up with a messy code with lots of hidden dependencies and global state. When you have more people working on the project you'll need even more structure. That's when it's important to introduce a common way to manage packages/libraries. When you have an open source project or when you know other projects import the code from your project repository that's when it's important to have private (aka `internal`) packages and code. Clone the repository, keep what you need and delete everything else! Just because it's there it doesn't mean you have to use it all. None of these patterns are used in every single project. Even the `vendor` pattern is not universal.
 
 With Go 1.14 [`Go Modules`](https://github.com/golang/go/wiki/Modules) are finally ready for production. Use [`Go Modules`](https://blog.golang.org/using-go-modules) unless you have a specific reason not to use them and if you do then you don’t need to worry about $GOPATH and where you put your project. The basic `go.mod` file in the repo assumes your project is hosted on GitHub, but it's not a requirement. The module path can be anything though the first module path component should have a dot in its name (the current version of Go doesn't enforce it anymore, but if you are using slightly older versions don't be surprised if your builds fail without it). See Issues [`37554`](https://github.com/golang/go/issues/37554) and [`32819`](https://github.com/golang/go/issues/32819) if you want to know more about it.
 

README_es.md

@@ -11,6 +11,7 @@ Traducciones:
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 ## Resumen
 

README_fr.md

@@ -11,6 +11,7 @@ Traductions:
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 ## Introduction
 

README_ja.md

@@ -11,6 +11,7 @@
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 ## 概要
 

README_ko.md

@@ -11,6 +11,7 @@
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 ## 개요
 

README_ptBR.md

@@ -11,6 +11,7 @@ Traduções:
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 ## Visão geral
 

README_ro.md

@@ -2,12 +2,14 @@
 
 Traduceri:
 
+* [English](README.md)
 * [한국어 문서](README_ko.md)
 * [简体中文](README_zh.md)
 * [正體中文](README_zh-TW.md)
 * [简体中文](README_zh-CN.md) - ???
 * [Français](README_fr.md)
 * [日本語](README_ja.md)
+* [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
 * [Română](README_ro.md)
 

README_zh-CN.md

@@ -9,6 +9,7 @@
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 这是Go应用程序项目的基础布局。这不是Go核心开发团队定义的官方标准；无论是在经典项目还是在新兴的项目中，这都是Go生态系统中一组常见的项目布局模式。这其中有一些模式比另外的一些更受欢迎。它通过几个支撑目录为任何足够大规模的实际应用程序提供一些增强功能。
 

README_zh-TW.md

@@ -11,6 +11,7 @@
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 這是 Go 應用程式專案的基本目錄結構。它不是核心 Go 開發團隊定義的官方標準；然而，它是 Go 生態系統中一組常見的老專案和新專案的目錄結構。其中一些目錄結構比其他目錄結構更受歡迎。這個專案目錄結構還有一些細微的改進，可以支援任何大型且實用的應用程式目錄結構。
 

README_zh.md

@@ -11,6 +11,7 @@
 * [日本語](README_ja.md)
 * [Portuguese](README_ptBR.md)
 * [Español](README_es.md)
+* [Română](README_ro.md)
 
 这是 Go 应用程序项目的基本布局。它不是核心 Go 开发团队定义的官方标准；然而，它是 Go 生态系统中一组常见的老项目和新项目的布局模式。其中一些模式比其他模式更受欢迎。它还具有许多小的增强，以及对任何足够大的实际应用程序通用的几个支持目录。