Markdown table fixes.

Author: pcj

README.md

@@ -215,7 +215,7 @@ that the file
 in the package `google.protobuf`.
 
 2. *Can the `cc_proto_library` rule "see" the generated protobuf
-   files* (in this case `descriptor.pb.{h,cc}`.  Just because the file
+   files*? (in this case `descriptor.pb.{h,cc}`.  Just because the file
    was imported does not imply that protoc will generate outputs for
    it, so somewhere in the `cc_library` rule dependency chain these
    files must be present.  This could be via another
@@ -224,8 +224,8 @@ in the package `google.protobuf`.
    specify that in the `proto_deps` attribute to the calling
    `cc_proto_library` rule.  Otherwise, pass a label that includes the
    (pregenerated) protobuf files to the `deps` attribute, just as you
-   would any typical `cc_library` rule.Hopefully that made sense.
-   It's tricky.
+   would any typical `cc_library` rule.  Hopefully that made sense.
+   It's a bit tricky.
 
 # Contributing
 

bzl/README.md

@@ -5,29 +5,18 @@ lists attributes and behavior that is shared across all languages.
 # `*_proto_compile` attributes
 
 | Name | Type | Description | Default |
-
+| ---- | ---- | ----------- | ------- |
 | `name` | `string` | The name of the rule (required) | `""` |
-
 | `protos` | `label_list` of file type `.proto` | The set of protobuf source files to compile. Must not be empty.  | `[]` |
-
 | `proto_deps` | `label_list` having provider `proto` | A list of `*_proto_library` that the calling rule is dependent upon. | `[]` |
-
 | `protoc` | executable `label` | Used to override the default protoc binary tool. | `//external:protoc` |
-
 | `gen_{LANG}` | `boolean` | Enable/disable protobuf output on a language-specific basis. | Usually `True` |
-
 | `gen_{LANG}_grpc` | `boolean` | Enable/disable gRPC output on a language-specific basis. | `False` |
-
 | `gen_{LANG}_protobuf_binary` | executable `label` | Use to override the plugin executable on a language-specific basis.  This attribute will not exist if this the language does not require a plugin for it. | *Implementation-specific* |
-
 | `gen_{LANG}_protobuf_options` | `string_list` | Additional options to be bundled into to the `--{LANG}_out` argument. | `[]` |
-
 | `gen_{LANG}_grpc_binary` | executable `label` | Use to override the grpc plugin executable on a language-specific basis.  This attribute will not exist if this the language does support or require a plugin for this. | *Implementation-specific* |
-
 | `gen_{LANG}_grpc_options` | `string_list` | Additional options to be bundled into to the `--grpc-{LANG}_out` argument. | `[]` |
-
 | `outs` | `output_list` | Permits language implementation to specify additional implicit output targets.  Currently only used by the java implementations which expose `%{name}.srcjar` as an implicit handle to the generated sourcefiles.` | `{}` |
-
 | `output_to_workspace` | `boolean` | Under normal operation, generated code is placed in the bazel sandbox and does not need to be checked in into version control.  However, your requirements may be such that is necessary to check these generated files in.  Setting this flag to `True` will emit generated `*.pb.*` files into in your workspace alongside the `*.proto` source files.  Please make sure you're sure you want to do this as it has the potential for unwanted overwrite of source files.  | `False` |
 
 
@@ -38,7 +27,7 @@ The attributes `protoc`, `protos`, `proto_deps`, `imports`,
 `*_proto_library` rules, as described above.
 
 | Name | Type | Description | Default |
-
+| ---- | ---- | ----------- | ------- |
 | `name` | `string` | The name of the library rule (required).  The implicit output target `%{name}.pb` refers to the corresponding proto_compile rule. | `""` |
 | `proto_args` | `dict` | A dictionary of arguments to be passed to the `*_proto_compile` implementation. | `{}` |
 | `srcs` | `label_list` of file type specific to library rule | Additional source files passed to the implementing library rule (for example, `cc_library`  | `[]` |

bzl/go/README.md

@@ -120,7 +120,6 @@ the protobuf library rule name, in which case part III is not needed.
 The go rules include all common attributes in addition to:
 
 | Name | Type | Description | Default |
-
+| ---- | ---- | ----------- | ------- |
 | `go_import_map` | `string_dict` | A set of mappings from protobuf imports to go imports. | `{}` |
-
 | `go_prefix` | `label` of provider go_prefix (from rules_go). | The go prefix that should be used be code generated by this rule. | `//:go_prefix` |

bzl/grpc_gateway/README.md

@@ -85,7 +85,7 @@ grpc_gateway_binary(
 The grpc_gateway rules include all common attributes in addition to go rule attributes in addition to:
 
 | Name | Type | Description | Default |
-
+| ---- | ---- | ----------- | ------- |
 | `log_level` | `int` | Logging threshold level. | `0` |
 | `log_dir` | `string` | Log directory pathname. | `""` |
 | `log_backtrace_at` | `int` | See grpc_gateway docs. | `0` |