Fix minor text wrapping nits.

Co-authored-by: Divya Mohan <[email protected]>

Author: shannonxtreme

content/en/docs/tasks/configmap-secret/managing-secret-using-config-file.md

@@ -34,8 +34,8 @@ The following example stores two strings in a Secret using the `data` field.
    ```
 
    {{< note >}}
-   The serialized JSON and YAML values of Secret data are encoded as base64
-   strings. Newlines are not valid within these strings and must be omitted. When using the `base64` utility on Darwin/macOS, users should avoid using the `-b` option to split long lines. Conversely, Linux users *should* add the option `-w 0` to `base64` commands or the pipeline `base64 | tr -d '\n'` if the `-w` option is not available. {{< /note >}}
+   The serialized JSON and YAML values of Secret data are encoded as base64 strings. Newlines are not valid within these strings and must be omitted. When using the `base64` utility on Darwin/macOS, users should avoid using the `-b` option to split long lines. Conversely, Linux users *should* add the option `-w 0` to `base64` commands or the pipeline `base64 | tr -d '\n'` if the `-w` option is not available.
+   {{< /note >}}
 
    The output is similar to:
 
@@ -134,7 +134,9 @@ type: Opaque
 
 ### Specifying both `data` and `stringData`
 
-If you specify a field in both `data` and `stringData`, the value from `stringData` is used. For example, if you define the following Secret:
+If you specify a field in both `data` and `stringData`, the value from `stringData` is used.
+
+For example, if you define the following Secret:
 
 ```yaml
 apiVersion: v1

content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md

@@ -111,7 +111,9 @@ username:    5 bytes
 
 The commands `kubectl get` and `kubectl describe` avoid showing the contents
 of a `Secret` by default. This is to protect the `Secret` from being exposed
-accidentally, or from being stored in a terminal log. To check the actual content of the encoded data, please refer to [Decoding the Secret](#decoding-secret).
+accidentally, or from being stored in a terminal log.
+
+To check the actual content of the encoded data, please refer to [Decoding the Secret](#decoding-secret).
 
 ## Decoding the Secret  {#decoding-secret}